Rolling and Manual deployments corrections #5265
Conversation
|
|
||
| {{< note theme="info" >}} | ||
|
|
||
| If the last deployment failed, you can only use the default stop-start strategy. |
There was a problem hiding this comment.
Do we want to elaborate on why ?
There was a problem hiding this comment.
I agree it would be helpful to elaborate
catplat
left a comment
catplat
left a comment
There was a problem hiding this comment.
Suggested several edits and made comments
|
|
||
| {{< note theme="info" >}} | ||
|
|
||
| If the last deployment failed, you can only use the default stop-start strategy. |
There was a problem hiding this comment.
I agree it would be helpful to elaborate
| - When deployment is complete, the clone of your app is shut down and removed. | ||
| - All traffic and services are now solely applied to the original app alone. | ||
| - The original app is updated with the new code and configuration. | ||
| - The deploy hook is run on the original app. |
There was a problem hiding this comment.
Is the deploy hook the only thing that is run? Are pre-start commands also run? (Wondering if we need to map this more closely to the steps in the "Deploy steps" section)
| **You are billed for extra resources while both app versions active.** If your app’s deployment phase takes longer and uses more resources, expect proportionally higher costs. | ||
| {{< /note >}} | ||
|
|
||
| ### Deployment strategies |
There was a problem hiding this comment.
What if we made this a H2 instead of H3, so it's at the same level as "deployment type" and not buried in ZDD content? Additionally, what if we made ZDD headings subheadings of Rolling deployment - assuming the goal is treating ZDD as just the implementation of the rolling deployment strategy?
5 participants
What's changed
All the points are IMHO, please feel free to reject.
Manual Deployments
ZDD
Where are changes
Updates are for:
sites/platformtemplates)sites/upsuntemplates)