Jira (PUP-2821) disable_warnings setting is inert in [master]

[Russell Mull (JIRA)]

Russell Mull updated an issue

Puppet / PUP-2821 disable_warnings setting is inert in [master] Change By: Russell Mull Summary: disable_warnings  section  setting  is inert in [master] Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Branan Riley (JIRA)]

Branan Riley updated an issue

Puppet / PUP-2821 disable_warnings setting is inert in [master]

Change By: Branan Riley Labels: triaged

Add Comment

[Moses Mendoza (JIRA)]

Moses Mendoza updated an issue

Puppet / PUP-2821 disable_warnings setting is inert in [master]

Change By: Moses Mendoza Labels: triaged

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper commented on PUP-2821

Re: disable_warnings setting is inert in [master] Looks to work correctly now. Without the setting, the server log prints: 2019-10-01T20:43:14.323Z WARN [qtp1893470395-81] [puppetserver] Puppet This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Integer. There is further documentation for validate_legacy function in the README. at ["/etc/puppetlabs/code/environments/production/manifests/site.pp", 1]: If I add the setting to the master section, and reload puppetserver then no more warning [root@deuaydeq4o5qqbi ~]# puppet config set disable_warnings deprecations --section master [root@deuaydeq4o5qqbi ~]# puppetserver reload [root@deuaydeq4o5qqbi ~]# puppet agent -t Then server log doesn't show deprecation warning: 2019-10-01T20:44:56.072Z INFO [qtp1658177334-125] [puppetserver] Scope(Class[main]) 2019-10-01T20:44:56.078Z INFO [qtp1658177334-125] [puppetserver] Puppet Compiled catalog for deuaydeq4o5qqbi.delivery.puppetlabs.net in environment production in 0.21 seconds I'm guessing this was fixed in PUP-7611 and commit 7ed67a7726cfb96c1c2673a1b6825e737b605053

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)