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

(PDK-575) Run puppet parser validate with an dummy empty puppet.conf #402

Merged
merged 1 commit into from
Feb 1, 2018

Conversation

rodjek
Copy link
Contributor

@rodjek rodjek commented Jan 12, 2018

To prevent any user or system level puppet.conf settings from interfering with the behaviour of the PDK, pass /dev/null or NUL (depending on the platform) as the puppet.conf when running puppet parser validate.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.006%) to 93.228% when pulling 6c86948 on rodjek:pdk-575 into 89fb414 on puppetlabs:master.

@@ -36,7 +40,7 @@
let(:options) { { auto_correct: true } }

it 'has no effect' do
expect(command_args).to eq(%w[parser validate].concat(targets))
expect(command_args).to eq(%w[parser validate --config /dev/null].concat(targets))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the purpose of this existing auto_correct test assertion to make sure that some option is not being added? If so should we maybe just assert that the option is absent rather than having to update this test every time the invocation changes?

Also should we have a new test that explicitly checks for the --config param?

@bmjen bmjen merged commit dd74bb2 into puppetlabs:master Feb 1, 2018
@rodjek rodjek deleted the pdk-575 branch February 1, 2018 01:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants