Project

General

Profile

Bug #11038

Per-environment future parser settings do not seem to work in the Foreman smart-proxy puppet parser.

Added by Jason Smith about 6 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Puppet
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Puppet 3.7.5 added per-environment future parser settings, which was released just a few months ago. If the current parser is enabled in the global puppet.conf but the future parser is enabled in just one or a few directory environments, then the Foreman smart-proxy parser fails to detect that the future parser is enabled and produces syntax errors when parsing these "future" environments if they contain any new constructs. See Issue #2878 for an earlier bug and its fix.

History

#1 Updated by Dominic Cleal about 6 years ago

  • Category set to Puppet

#2 Updated by Ewoud Kohl van Wijngaarden over 3 years ago

  • Status changed from New to Rejected

Now that we're moving past Puppet 3 I think we can consider this as something we're not going to fix anymore.

Also available in: Atom PDF