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

Modulesync, use rspec-puppet-facts and fix tests #111

Merged
merged 10 commits into from
Nov 25, 2018
Merged

Conversation

alexjfisher
Copy link
Member

No description provided.

@@ -0,0 +1,29 @@
---
Copy link
Member

Choose a reason for hiding this comment

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

I do wonder about excluding this (and the other nodesets) from .sync.yml

Copy link
Member Author

Choose a reason for hiding this comment

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

I've opened #112 since the tests aren't running at all at the moment, (and I think there was enough going on already in this PR.)

operatingsystemmajrelease: releasenum
}
end
on_supported_os(facterversion: '3.6').each do |os, facts|
Copy link
Member

Choose a reason for hiding this comment

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

There must be a better way to do this. It can be set via an env var so should we fix this in the spec helper? Can we set it via a custom fact?

Copy link
Member Author

Choose a reason for hiding this comment

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

yeah, that'd make sense. We could set it to a different version depending on whether we're testing against puppet 4, 5 or 6? IIRC, I've been using 3.6 as that's the version that puppet Inc ships with puppet 4.10.

@alexjfisher alexjfisher merged commit def0dd8 into master Nov 25, 2018
@bastelfreak bastelfreak deleted the modulesync branch November 26, 2018 11:10
@alexjfisher alexjfisher changed the title Modulesync and fix tests Modulesync, use rspec-puppet-facts and fix tests Nov 26, 2018
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.

4 participants