Puppet 5.5.6 will emit deprecation warnings for ca related settings even if the setting is never set on the CLI or in settings:
{noformat} $ bx puppet agent -t Warning: Accessing 'ca' as a setting is deprecated. (location: /Users/josh/work/puppet/lib/puppet/settings.rb:1165:in `issue_deprecation_warning') Exiting; no certificate found and waitforcert is disabled {noformat}
This is my bad, I recommended using deprecated completely and forgot it's behaved that way. We instead need to add a hook that fires when should remove these warning from the deprecated settings are set entirely, as they are not read going to be moved in Puppet 6.
Puppet 5.5.6 will emit deprecation warnings for ca related settings even if the setting is never set on the CLI or in settings:
{noformat} $ bx puppet agent -t Warning: Accessing 'ca' as a setting is deprecated. (location: /Users/josh/work/puppet/lib/puppet/settings.rb:1165:in `issue_deprecation_warning') Exiting; no certificate found and waitforcert is disabled {noformat}
We should remove these warning from the settings entirely, as they are not going to will still be moved available in Puppet 6.
We are no longer deprecating CA-related settings (see PUP-9027 for list of settings that were deprecated and are being undeprecated). We are no longer removing these settings in Puppet 6.