Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Feedback on page: /guides/v2.2/cloud/deploy/reduce-downtime.html #4255

Closed
kotasthanesp opened this issue Apr 15, 2019 · 2 comments
Closed

Feedback on page: /guides/v2.2/cloud/deploy/reduce-downtime.html #4255

kotasthanesp opened this issue Apr 15, 2019 · 2 comments
Assignees
Labels
2.x Internal Dev Differentiates work between community and Magento staff

Comments

@kotasthanesp
Copy link

General issue

confusion about minimum ece-tools version needed for 0-downtime deploy

Description:

"Upgrade to the ece-tools package or update the ece-tools version
Your Magento Commerce Cloud project must have the latest ece-tools package so that you have the tools available to configure an optimal deployment. If you have the latest ece-tools, continue to the next step."
Actually, 0-downtime deploys are possible to achieve once merchants have 2002.0.13. But the para above suggests that to achieve 0-downtime deploys merchants have to be on latest ece-tools (else, they should not proceed to successive steps to achieve 0-downtime deploy.
My concern is that this could be interpreted wrongly, and many merchants who are on .14, .15, .16, etc. won't try to go through this article themselves, because each month a new ece-tools version comes out. This affects adoption of 0-downtime deploy functionality.

Possible solutions:

while, it is a good idea to always be on latest ece-tools version, we could state that 0-downtime deploys are achievable starting 2002.0.13. We do this already in release notes

Additional information:

@hguthrie
Copy link
Contributor

hguthrie commented May 6, 2019

Good point. I noted the best practice is to use latest, but that zero-downtime method works with 2002.0.13 and later versions. Thanks!

@hguthrie hguthrie added 2.x Internal Dev Differentiates work between community and Magento staff labels May 6, 2019
hguthrie added a commit that referenced this issue May 6, 2019
@dobooth
Copy link
Contributor

dobooth commented May 7, 2019

Fixed with merge.

@dobooth dobooth closed this as completed May 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
2.x Internal Dev Differentiates work between community and Magento staff
Projects
None yet
Development

No branches or pull requests

3 participants