-
-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permission contention on hiera.yaml between module and PE #260
Conversation
} | ||
else { | ||
# It would probably be better to assume this is puppetserver, but that | ||
# would be a backwards-incompatible change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're about to make one anyway when we drop support for puppet 4. Maybe this is a good time?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not opposed to it, but I'd really like to get a new version with this fix in immediately for the PE issue (it's restarting pe-puppetserver every 30 minutes because of this) and not worry about the backwards-incompatibility at the same time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok. I'll call off 3.4.1 and we can do a 3.5.0 instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, I should remember to use 'hide whitespace changes' more often to make it clear to me that this isn't something you had written...
@rnelson0 Are there any tests you'd like to add/modify? |
Fixes #245
Replaces #246
Sets better defaults for
/etc/hiera.yaml
, eyaml keys, etc., to prevent conflict with the latest Puppet Enterprise versions.