Rebase to a different Deployment.

PUT {{baseUrl}}/orgs/:orgId/apps/:appId/envs/:envId/from_deploy_id

Rebasing an Environment means that the next Deployment to the Environment will be based on the Deployment specified in the rebase rather than the last one in the Environment. The Deployment to rebase to can either be current or a previous Deployment. The Deployment can be from any Environment of the same Application.

Running code will only be affected on the next Deployment to the Environment.

Common use cases for rebasing an Environment:

• Rollback: Rebasing to a previous Deployment in the current Environment and then Deploying without additional changes will execute a rollback to the previous Deployment state.

• Clone: Rebasing to the current Deployment in a different Environment and then deploying without additional changes will clone all of the configuration of the other Environment into the current one. (NOTE: External Resources will not be cloned in the process - the current External Resources of the Environment will remain unchanged and will be used by the deployed Application in the Environment.

Request Body

["a", "d", " ", "o", "f", "f", "i", "c", "i", "a"]

HEADERS