-
Notifications
You must be signed in to change notification settings - Fork 12
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
Feature/bseng 1937/upgrade unit by unit #237
Feature/bseng 1937/upgrade unit by unit #237
Conversation
Add UnitUpgradeStep and is_unit_upgrade_step, also use sub_steps as property to prevent defining it as not list of BaseStep's. Raising TypeError in add_step if object is not based on BaseStep.
Like this, we can upgrade packages in individual step for each unit and run these steps in parallel or sequentially. Right now, it's run sequentially, so no change in previous approach.
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.
Looks good, and glad that we are updating documentation to align. I just have one question.
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.
LGTM
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.
LGTM
Add UnitUpgradeStep and is_unit_upgrade_step, also use sub_steps as
property to prevent defining it as not list of BaseStep's. Raising
TypeError in add_step if object is not based on BaseStep.
Use UnitUpgradeStep, we can upgrade packages in individual step for each unit and
run these steps in parallel or sequentially. Right now, it's run
sequentially, so no change in previous approach.