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
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
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:
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: