-
Notifications
You must be signed in to change notification settings - Fork 897
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
[WIP] Flatten worker settings #20975
base: master
Are you sure you want to change the base?
Conversation
51e090c
to
98f5476
Compare
good simplification! |
98f5476
to
1e8242f
Compare
1e8242f
to
fdf09ab
Compare
From Pull Request: ManageIQ/manageiq#20975
From Pull Request: ManageIQ/manageiq#20975
3985502
to
13044af
Compare
13044af
to
d166e42
Compare
Checked commit Fryguy@d166e42 with ruby 2.6.3, rubocop 0.82.0, haml-lint 0.35.0, and yamllint app/models/miq_worker.rb
|
This pull request is not mergeable. Please rebase and repush. |
Do we want to still move forward with this? |
From Pull Request: ManageIQ/manageiq#20975
I still want to move forward with this, but need to rework it, possibly to remove the inheritance entirely. I had spoken to @jrafanie a while back and didn't want to step on the work he was doing to fix the UI form. In that thread we discussed possibly dropping the inheritance entirely, which would mean this PR would stay, but it would be even less complicated. |
This pull request has been automatically closed because it has not been updated for at least 3 months. Feel free to reopen this pull request if these changes are still valid. Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation. |
From Pull Request: ManageIQ/manageiq#20975
This pull request is not mergeable. Please rebase and repush. |
This PR flattens the complicated nesting of the worker settings in order to make it easier for end users to find what they are looking for. In particular, since YAML is whitespace delimited, it can be very easy to mess up the yaml nesting, and this should fix that problem. One downside of going from a tree structure to a flat structure is that you lose context of what is inherited. As such, this PR introduces a new key in the settings,
:inherited_from
which acts more like a comment to the editor and cannot be modified by the end user. However, with that information, they should be able to easily traverse up the inheritance chain to determine the values.cc @jrafanie
WIP because