-
Notifications
You must be signed in to change notification settings - Fork 104
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-1200) Fix bundle env handling with puppet-dev #579
Conversation
end | ||
end | ||
end | ||
TESTFILE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This method seems a little round-about to me...
Could we update the test manifest to have two specific tests that assert either the presence or absence of the path
key and then below use pdk test unit --tests=
to only invoke the specific test and assert that it passed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated the test to expect the path... so the acceptance test was simplified to expect a PDK test success or failure.
Should this change also be applied to |
ee0e1d8
to
818b9e8
Compare
Bundler requires that you continue to pass in PUPPET_GEM_VERSION when doing check, install, and exec. Previously we were only setting the puppet gem env when doing a bundle check and updating the lock file.
cdbf095
to
a3737da
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Bundler requires that you continue to pass in PUPPET_GEM_VERSION
when doing check, install, and exec. Previously we were only setting
the puppet gem env when doing a bundle check and updating the lock file.