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

Flatten worker settings #684

Closed
wants to merge 1 commit into from

Conversation

Fryguy
Copy link
Member

@Fryguy Fryguy commented Jan 25, 2021

Comment on lines +132 to +134
:ems_metrics_collector_worker:
:ems_metrics_gnocchi_granularity: 300
:ems_metrics_openstack_default_service: "auto"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@agrare As discussed we should open a separate issue to not "infect" the base setting, but instead use the ems.ems_openstack section for these.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wondering if these should become settings per provider. in general, wondering whether global settings for provider workers makes sense.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ideally, yes, these should be per-provider-instance settings, though unfortunately I don't think we don't have a mechanism for that at the moment (without making it part of the "create provider" form)

Comment on lines +145 to +146
:event_catcher:
:event_catcher_openstack_service: "auto"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto for these.

@Fryguy Fryguy force-pushed the flatten_worker_settings branch from 9ed95b1 to 0164615 Compare February 3, 2021 21:03
@miq-bot
Copy link
Member

miq-bot commented Feb 3, 2021

Checked commit Fryguy@0164615 with ruby 2.6.3, rubocop 0.82.0, haml-lint 0.35.0, and yamllint
3 files checked, 0 offenses detected
Everything looks fine. ⭐

@@ -420,7 +420,7 @@ def parse_datetime(datetime)
end

def metric_service_from_settings
Settings[:workers][:worker_base][:queue_worker_base][:ems_metrics_collector_worker][:ems_metrics_openstack_default_service]
Settings.workers.ems_metrics_collector_worker.ems_metrics_openstack_default_service
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@agrare I don't understand how this could have blown up previously. Like why is this rescued with StandardError?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤷 looks like it was added here ManageIQ/manageiq#13918

Looks like he was worried about the settings not being there?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strangely, the code doesn't care if the key is there but the value is nil, even though the log message talks about a nil value 🤷‍♂️

I can tweak this in a follow up to make more sense.

@miq-bot
Copy link
Member

miq-bot commented Mar 6, 2023

This pull request has been automatically marked as stale because it has not been updated for at least 3 months.

If these changes are still valid, please remove the stale label, make any changes requested by reviewers (if any), and ensure that this issue is being looked at by the assigned/reviewer(s)

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

@miq-bot miq-bot closed this Jun 12, 2023
@miq-bot
Copy link
Member

miq-bot commented Jun 12, 2023

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.

@Fryguy Fryguy removed the stale label Jul 27, 2023
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