-
Notifications
You must be signed in to change notification settings - Fork 898
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
Add call for bundled service children retirement #17317
Add call for bundled service children retirement #17317
Conversation
@miq-bot add_label retirement |
8bda8ad
to
047a5b5
Compare
@tinaafitz can you please 👀 |
Checked commit d-m-u@047a5b5 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bump @mkanoor @gmcculloug |
bump @mkanoor 👻 |
parent_service.service_resources.collect do |svc_rsc| | ||
next unless svc_rsc.resource.present? && svc_rsc.resource.respond_to?(:retire_now) | ||
next if svc_rsc.resource.type.blank? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@d-m-u
Can we validate that this code gets executed. According to @tinaafitz a child service would get marked as an blank resource type.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The top level service itself has a blank type and we're not creating task for it to retire in this method so we need this check. The child services do have types, they're type Vm or Service or Whatever.
All direct service children of the parent service in a bundled service need to go through the create_retire_subtasks method so that child vms get retired as well.
WIP'd cause requires automate changes.