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

Package foreman-release-scl -> latest #643

Closed
wants to merge 1 commit into from

Conversation

kotyara85
Copy link

If foreman version entirely managed by puppet migration to a newest version will fail is not up to date.
This's related mostly when used with $repo + $version.
Tested with fresh build + updates + upgrades

…ade foreman if we move to another version using puppet vars: version & repo
@sean797
Copy link
Member

sean797 commented Jul 27, 2018

@Chiccat I think I'd be okay with parameterizing this, leaving the default unchanged. Setting lastest could cause unintended consequences for some users, further the docs currently explicitly say "upgrade or install the SCL release".

@ekohl
Copy link
Member

ekohl commented Oct 8, 2018

Apologies for the slow response. We prefer defaulting to installed so I submitted #672 which allows changing the package state via hiera. I hope this works for you but otherwise we can expose it on the main class. I'm going to close this but feel free to continue the discussion or open a new PR based on mine.

@ekohl ekohl closed this Oct 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants