-
Notifications
You must be signed in to change notification settings - Fork 356
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
Renaming of provider_foreman files, code to configuration_manager #6756
Conversation
- Renamed views, controllers and other files to not be specific to provider_foreman - Renamed methods and actions, routes etc to use `configuration_manager` - Changed any links to point to `configuration_manager` instead of `provider_foreman` follow up PR for ManageIQ#6730
8e9a3c3
to
261e6ba
Compare
cacc376
to
ce2fcea
Compare
ce2fcea
to
095bd67
Compare
- Fixed issue introduced during renaming of modules in toolbar files that was caught by failure in controller spec test.
Some comments on commits h-kataria/manageiq-ui-classic@261e6ba~...852e5c3 spec/controllers/configuration_manager_controller_spec.rb
|
Checked commits h-kataria/manageiq-ui-classic@261e6ba~...852e5c3 with ruby 2.5.7, rubocop 0.69.0, haml-lint 0.20.0, and yamllint app/presenters/menu/default_menu.rb
spec/controllers/configuration_manager_controller_spec.rb
|
maybe @bdunne can run these changes against a Foreman/Satellite system to ensure it does not break the old flow. |
The change is totally okay from my side. However, I am a little worried about the amount of tech debt in the area. If we want to do future work here, we should probably consider increasing the consistency with the rest of the screens in order to avoid some pain in the future. cc @himdel |
Closed in favor of #6782 |
configuration_manager
configuration_manager
instead ofprovider_foreman
follow up PR for #6730
Depends on core PR ManageIQ/manageiq#19949