-
Notifications
You must be signed in to change notification settings - Fork 66
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
(BKR-1509) Beaker 4.0 Compatibility #62
Conversation
Some beaker-puppet workflows do not "require 'beaker'" before beaker-puppet. We should not assume that beaker is already in the environment: since it's a dependency, a simple require statement will take care of this.
There's no need to extend/require any specific module paths in pre-suite files: they pull the DSL extensions just the same as test suites do.
Since configure_pe_defaults_on has moved to beaker-pe, we need to simulate that method's effects to test the invocation of remove_#{type}_defaults_on. In this case, it depends on host['type'] being set for all hosts.
extend Beaker::DSL::InstallUtils | ||
|
||
SourcePath = Beaker::DSL::InstallUtils::SourcePath | ||
GitHubSig = Beaker::DSL::InstallUtils::GitHubSig |
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.
Do we not still need these references defined here?
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.
Nope. They're pulled into the DSL namespace, which is set up before pre-suite execution, so they're already available. In fact, these references aren't even complete, since they're relying on a previous chain of inclusion that no longer exists. Both of those constants are actually defined in FOSSUtils
, which is included in the DSL here via DSL.register
.
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.
That's super lovely
Assorted fixes for running puppet/acceptance that weren't caught during acceptance testing due to CI configuration conflicts.