-
Notifications
You must be signed in to change notification settings - Fork 268
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
Refactor repo handling #660
Conversation
I'll need to split out a few more things, work on tests and reorder a bit. Then I'll need to verify if there are more version specific workarounds we can get rid of. Also thinking about removing the explicit failures about an unsupported OS and setting values to undef so people can override where needed. |
852f3d4
to
95e6aa4
Compare
95e6aa4
to
151bbae
Compare
tests fail. |
34803fb
to
d6df712
Compare
this needs a rebase :) |
d6df712
to
981daf4
Compare
* Drop use of the 'stable' repository * Disallow releases/ as part of the repository * Add foreman-rails repository * Stop including foreman::params * Remove anchor pattern * Move to https
981daf4
to
bc46573
Compare
Updated to fix a bug in the yum handling. Debian nightlies are still broken so can't promise we don't have regressions there. |
merged, bedankt @ekohl! |
Will need #659 for the acceptance tests to pass.
Note that the foreman-rails repository assumes Foreman 1.17+ so that'll become the new minimum version. I'm going to continue with removing some compatibility with older versions in follow up PRs.