You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
Allow a complete plan to be run at a specific point in another plan.
Why is this needed:
Upgrade processes are often identical to the deploy plan, with the exception of a pre-upgrade step and a post-upgrade step. It would be preferable not to duplicate the deploy plan phases in the upgrade plan.
(I would not expect parameters that trigger the included plan to have any effect on the plan it is included in)
Example:
This is a cut-down code snippet of our operator.yaml that hopefully demonstrates what I mean.
plans:
deploy:
phases:
- name: deploy-initsteps:
- name: deploy-databasetasks:
- database-migratestrategy: serial
- name: deploy-configssteps:
- name: deploy-configtasks:
- apiserver-configstrategy: serial
- name: deploy-apiserversteps:
- name: deploy-apiservertasks:
- apiserverstrategy: serial
- name: deploy-virtualservicessteps:
- name: deploy-virtualservicestasks:
- virtualservicesstrategy: serial
- name: cleanupsteps:
- name: cleanuptasks:
- database-migrate-cleanupstrategy: serialstrategy: serialupgrade:
phases:
- name: offlinesteps:
- name: offlinetasks:
- take-app-offline
- name: backupsteps:
- name: backuptasks:
- backup-db
- name: upgradeincludePlan: deploy # upgrade is identical to deploy except that we need to take the application offline, backup the database, and bring the app online afterwards.
- name: onlinesteps:
- name: onlinetasks:
- bring-app-online
The text was updated successfully, but these errors were encountered:
What would you like to be added:
Allow a complete plan to be run at a specific point in another plan.
Why is this needed:
Upgrade processes are often identical to the deploy plan, with the exception of a pre-upgrade step and a post-upgrade step. It would be preferable not to duplicate the deploy plan phases in the upgrade plan.
(I would not expect parameters that trigger the included plan to have any effect on the plan it is included in)
Example:
This is a cut-down code snippet of our operator.yaml that hopefully demonstrates what I mean.
The text was updated successfully, but these errors were encountered: