-
Notifications
You must be signed in to change notification settings - Fork 297
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
Fixes #37471 - Support Zeitwerk loader #10997
Fixes #37471 - Support Zeitwerk loader #10997
Conversation
I had to check out:
I tested
Seems all good so far! I grepped development.log for |
also notable: With the foreman-tasks PR checked out, I did not see this error
which is currently failing in CI. |
8859c89
to
0c72da8
Compare
2b22e7c
to
711dc2b
Compare
66d1f0d
to
c3daa15
Compare
0f4329a
to
f30c895
Compare
48f3162
to
cb2a1ae
Compare
Ready to merge after theforeman/foreman#10131 is merged, dropped the commit for testing with Foreman PR, the latest run was green: |
cb2a1ae
to
a7bc48d
Compare
@ofedoren any idea why the tests are failing? |
The failures in |
@jeremylenz can you merge it then? :) |
WIPWhat are the changes introduced in this pull request?
This PR should make Katello plugin compatible with Zeitwerk autoloader, which will be enabled in Foreman instead of classic Rails' loader.
Considerations taken when implementing this change?
I was trying to change rather less than more. Although, some stuff (like CV acronym) can be introduced, but will require more changes and I'm not sure it'll be quite safe. It's up to maintainers.
What are the testing steps for this pull request?
Test with Foreman main PR (included in CI workflow) and hope for the best. Note: at first it'll be red, since some plugins, which are dependencies, should be updated as well. Additionally, after the tests are green I strongly recommend to test out basic/advanced content related workflows live.