Skip to content

(maint) Fix module installing in master-agent scenario #242

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

Merged
merged 1 commit into from
Jan 24, 2019

Conversation

glennsarti
Copy link
Contributor

Previously the powershell module was only being installed onto the
default host. However this meant the module was only being installed
onto the agent, not the server, which then caused issues during tests
because the module content was not 'file syncd' from the master and
tests were failing as it couldn't find the powershell provider.

This commit uses the module install helper from beaker to install on
all hosts.

Previously the powershell module was only being installed onto the
default host.  However this meant the module was only being installed
onto the agent, not the server, which then caused issues during tests
because the module content was not 'file syncd' from the master and
tests were failing as it couldn't find the powershell provider.

This commit uses the module install helper from beaker to install on
all hosts.
@glennsarti
Copy link
Contributor Author

Running through adhoc...

@michaeltlombardi michaeltlombardi merged commit a33a258 into puppetlabs:master Jan 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants