Skip to content
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

Support strict_variables by removing dynamic lookups #21

Closed

Conversation

hashbrowncipher
Copy link

This pull request removes a bunch of existing functionality. I would understand if you don't want to merge it.

My organization would like to enable strict_variables for our Puppet compilation. The current design of this module is not compatible with strict_variables, because it uses dynamic lookups to test for parameters. Dynamic lookups are deprecated.

With that in mind, I propose to remove these lookups entirely in favor of class parameters.

@razorsedge
Copy link
Contributor

Oh boy.

So I just familiarized myself with strict_variables. I think I understand it's intent, but I now will have to overhaul every one of my modules and drop support for setting global variables via Dashboard (or some other ENC). :-(

And to be pedantic: this module checks for top-scope variables and does not utilize dynamic lookups.

@razorsedge razorsedge added bug Something isn't working enhancement New feature or request labels Sep 22, 2014
@razorsedge razorsedge self-assigned this Jan 6, 2015
@vStone
Copy link
Contributor

vStone commented Oct 8, 2015

This is getting necessary for newer puppet versions.

@mterzo
Copy link

mterzo commented Jun 24, 2016

Glanced at the patch, doesn't look like they are params which won't allow for modifaction.

@razorsedge razorsedge mentioned this pull request Sep 7, 2016
@jnquintin
Copy link

The pull request PR#79 correct the issue while allowing the modifications

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants