MongoDB

When making changes to your application through the <a href="https://www.mongodb.com/docs/atlas/app-services/manage-apps/deploy/manual/deploy-ui/" rel="nofollow noopener noreferrer" target="_blank">Atlas App Services UI</a> or <a href="https://www.mongodb.com/docs/atlas/app-services/admin/api/v3/#draft-and-deploy-a-group-of-changes" rel="nofollow noopener noreferrer" target="_blank">Atlas App Services API</a>, the changes are automatically saved in a draft state. Before these draft changes are deployed, they are not visible to end users and do not affect the production application.

Changes made using <a href="https://www.mongodb.com/docs/atlas/app-services/manage-apps/deploy/automated/deploy-automatically-with-github/" rel="nofollow noopener noreferrer" target="_blank">automatic GitHub deployment</a> or the <a href="https://www.mongodb.com/docs/atlas/app-services/manage-apps/deploy/manual/deploy-cli/" rel="nofollow noopener noreferrer" target="_blank">App Services CLI</a> are deployed independently of draft changes.

If you have draft changes waiting to be deployed, a blue banner is present at the top of the App Services UI with the options to Review &amp; Discard or Review &amp; Deploy.

After clicking Review &amp; Deploy, a green banner at the top of the App Services UI provides the option to <a href="https://www.mongodb.com/docs/atlas/app-services/manage-apps/deploy/#deployment-history" rel="nofollow noopener noreferrer" target="_blank">View Deployment History</a>.

For more information on reviewing and deploying changes, see <a href="https://www.mongodb.com/docs/atlas/app-services/manage-apps/deploy/manual/deploy-ui/" rel="nofollow noopener noreferrer" target="_blank">Deploy from the Atlas App Services UI</a>.