Extension Deployment

2 min

Use Mission Control to deploy the specified Commerce extensions code version to the target instance in Optimizely Configured Commerce.

Note

Configured Commerce uses a rolling deploy strategy for its environments, ensuring there are always containers available to the load balancer. This means that even during a deploy, websites should be fully available to customers.

Steps

Go to Customers and select a customer.

Select a target Configured Commerce instance.

Click Actions on the instance page and select Extension Deployment.

(Optional) Schedule the action by toggling Scheduled Execution to On and selecting a time and date.

Review the details to confirm the selected instance (and scheduled time, if selected). You can ignore any greyed-out or immutable fields because they are for development or debugging.

Select the desired extensions version from the Version dropdown list.

Click Continue. If scheduled, the action runs at the specified time. Otherwise, the action runs immediately.

Wait until the status is marked as Complete on the Action Request page. If the action fails, submit a ticket with Optimizely Support with a link to the failed action request page.

Warning

This action supports deploying available extension builds on the current base code version for the given instance. You can deploy a version that is older than what is currently deployed if it is on the same base code version, but this is not recommended. This functionality exists so older versions can be deployed to sandbox instances more easily if a broken build is pushed. Optimizely does not recommend deploying old extension versions outside its existing use case; this could result in catastrophic data issues between conflicting extension versions, leading to downtime or other serious implications for the target instance.