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

Deprecation warning when adding worker_processes through hiera #655

Closed
ege1 opened this issue Jul 2, 2015 · 5 comments
Closed

Deprecation warning when adding worker_processes through hiera #655

ege1 opened this issue Jul 2, 2015 · 5 comments

Comments

@ege1
Copy link

ege1 commented Jul 2, 2015

Hi,

as soon as I set
nginx::worker_processes: 2

Through hiera, I get the deprecation warning:

Notice: [nginx] * DEPRECATION WARNING*: HI! I notice that you're declaring some attributes in Class[nginx]. It is highly recommended to set these values via Hiera going forward. This will become mandatory in the near future. Please check out https://github.com/jfryman/puppet-nginx/blob/master/docs/hiera.md for more information.

I just removed the check for worker_processes to get around this message (because otherwise foreman always reports changes on the host), so this is not an issue to me.

So just so you know.

Kind Regards,

Erik

@PierreR PierreR mentioned this issue Aug 10, 2015
@PierreR
Copy link
Contributor

PierreR commented Aug 10, 2015

👍 Same issue for me see referenced issue :-(

@3flex
Copy link
Contributor

3flex commented Aug 10, 2015

@ege1 does the error go away when you set it like this?

nginx::config::worker_processes: 2

@PierreR
Copy link
Contributor

PierreR commented Aug 10, 2015

@3flex I am pretty sure It does not work with nginx::config::worker_processes (see #536) It is silently ignored unless you add include nginx::config (and at that point it fails ...). But yes the deprecation warning disappears.

As nobody seems able to give a working alternative, I would remove the deprecation warning all together ... I have been living with this WARNING for months ... The WARNING is plain wrong anyway as it does not know if the params comes from hiera or not ...

@3flex
Copy link
Contributor

3flex commented Aug 10, 2015

@jfryman might need to come up with an alternate solution that is a bit more robust than what we have at the moment... I agree the warning is not ideal in this case, and I'm not sure how best to re architect things to both match @jfryman's goals for the module's structure and also make things more user friendly.

@ege1
Copy link
Author

ege1 commented Aug 11, 2015

@3flex Thanks for that hint. Yes, that works just perfect for me. It is recognized and it stops the deprecation warning. And i do not have explicitly included the nginx::config

So for me this is solved that way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants