Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Status Future consideration
Categories Content Manager
Created by Guest
Created on Jun 6, 2023

Deployment API Documentation

The deployment API documentation doesn't really cover real world scenarios. There are quick samples of a line of PowerShell, but really, that's now how anyone deploys. Deployments are done from a CI/CD server. So the build server has to create a package, upload a package, start a deployment, complete a deployment, etc... There needs to be a better explanation of how the different steps work together. Additionally, since you call the API in PowerShell, can Optimizely provide basic scripts for each step, so at the bare minimum, someone could deploy a site without having to change anything. And then someone could customize the script if they wanted to.

  • Guest
    Jun 7, 2023

    I thought of a few ways that I struggled with this:

    1. For a deployment with two parts, start and complete... how to enable the ability to approve the first part of variouse CI/CD servers (Jenkins, Azure, Octopus, etc...)

    2. For deployments with multiple parts... how to maintain the deployment id

    3. How to set up deployments so you dont have to deploy through all the various environments, just to get up to production.

    4. Difference between deploying to an environment, vs moving code between environments