Docs Home → Atlas App Services
Deployment Draft
A deployment draft represents a group of App changes that you can deploy or discard as a single unit.
Deployment Method | Drafts Explicitly Used? | Draft Behavior |
|---|---|---|
Yes | Any changes you make to your App's configuration in the App Services UI will be
automatically saved as a draft that you can manually deploy,
unless you have disabled drafts in the settings. | |
Yes | You can use an API endpoint
to create a draft, then use other endpoints to make changes and deploy (or discard)
the draft. | |
No | You make changes to configuration files locally, and once you are ready to deploy
them, push them. Once you confirm your changes and push,
a draft automatically gets created and deployed. | |
No | You make changes to configuration files locally, and once you are ready to deploy
them, push them to GitHub or any CI/CD pipeline. Once you push,
a draft automatically gets created and deployed. |
Important
Draft Conflicts
Avoid having multiple users make conflicting changes in UI or API drafts at the same time. If there are multiple concurrent drafts that contain conflicting changes, you will not be able to deploy one or more of the drafts.