Extension Deployment

  • Updated

Mission Control is currently in beta, which is open to all partners of Optimizely Configured Commerce and invite-only for some customers. If you do not have access to Mission Control, Optimizely Support can run these actions on your behalf. Contact them with the needed configuration details and field values (if applicable).

For information on the Mission Control beta or to request access, contact your Customer Success Manager.

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

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

  1. Log into Mission Control.
  2. Go to Customers and select a customer.
  3. Select a target Configured Commerce instance.
  4. Click Actions on the instance page and select Extension Deployment.
  5. (Optional) Schedule the action by toggling Scheduled Execution to On and selecting a time and date.
  6. 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.
  7. Select the desired extensions version from the Version dropdown list.
  8. Click Continue. If scheduled, the action runs at the specified time. Otherwise, the action runs immediately.
  9. 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.

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.