Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: PDK 1.4.1
-
Component/s: None
-
Labels:
-
Template:customfield_10700 214675
-
Acceptance Criteria:
- deprecated directives in the user's puppet.conf do not cause syntax validation to produce a warning
-
Epic Link:
-
Method Found:Customer Feedback
-
Release Notes:Bug Fix
-
Release Notes Summary:`pdk validate` will no longer read any `puppet.conf` files that might exist on the user's host in the default locations (e.g. `/etc/puppet/puppet.conf`) when running Puppet manifest syntax validation.
-
QA Risk Assessment:Needs Assessment
Description
puppet-syntax should not complain about problems in files we don't care about, in this case specifically the user's puppet.conf:
david@davids:~/git/pdk/foo$ cat /home/david/.puppetlabs/etc/puppet/puppet.conf
|
configtimeout = 10
|
|
|
david@davids:~/git/pdk/foo$ ~/git/pdk/bin/pdk validate puppet
|
[✔] Checking Puppet manifest syntax (**/**.pp).
|
[✔] Checking Puppet manifest style (**/*.pp).
|
Warning: puppet-syntax: Setting configtimeout is deprecated.
|
: puppet-syntax: (at /home/david/.pdk/cache/ruby/2.3.0/gems/puppet-5.1.0/lib/puppet/settings.rb:1159:in `issue_deprecation_warning')
|
david@davids:~/git/pdk/foo$ echo $?
|
0
|
david@davids:~/git/pdk/foo$
|
Originally reported in https://github.com/puppetlabs/pdk/issues/304
Attachments
Issue Links
- relates to
-
-
- Closed
-
