Optimizely Customer Feedback

Describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues please head to Support or our Developer Community.

You can assign up to 10 votes in total. Thank you for your feedback!

Workspace DXP Cloud Services
Categories Code deployment
Created by Guest
Created on Jul 29, 2021

PaaS Portal API, ignore ZeroDownTimeMode for commerce package by default

We are currently changing our Azure Pipeline so that we can deploy using the Smooth Deploy feature. Initially our scripts were pushing both CMS and Commerce at the same time, avoiding to push them individually.

The introduction of the flag ZeroDownTimeMode on the script has an unwanted behavior. When specifying ReadOnly of ReadWrite and including the Commerce Manager package with the CMS package, the API throws a 500 error with the following message: API call failed! The error was: The remote server returned an error: (500) Internal Server Error. {"success":false,"errors":["Can not deploy with Zero downtime mode for commerce projects."],"result":null}.

I understand the error, but it also means I need to do two separated deployments in order to fully deploy both packages. Could it be possible for Optimizely team to make the PaaS Portal process the commerce package anyway, but by ignoring the ZeroDownTimeMode flag instead?

Thank you!

  • Guest
    Jul 30, 2021

    Hi Elias,

    Just wanted to reiterate that I'm not really looking in having Commerce Cloud to work with Smooth Deploy, but more in having PaaS Portal API to ignore the flag when passed. CMS would still deploy with the specified ZeroDownTimeMode and Commerce on his side would still deploy in a traditional fashion.

    Hopes that helped to understand the need.

    Thanks!

  • Admin
    Elias Lundmark
    Jul 30, 2021

    Thanks for the feedback! Unfortunately we do not officially support Smooth Deploy for Commerce Cloud at all right now as a lot of the features in Commerce relies on database operations and the ReadOnly mode would leave a Commerce site with very limited functionality. We are considering how we could solve this within Commerce.


    Deploying CMS and Commerce separately is an interesting idea, although it may be difficult for us to ensure data consistency - especially in rollback scenarios. We'll investigate if this is possible.