Deployment and Event History
Deploying an Application
To deploy an application, click the "Deploy" button in the "Service info" card in the overview tab or use the "Deploy" option in the three-dot menu on the top-right corner. Review the unapplied changes, add a deployment note and click deploy.
Any configuration changes done will only come into effect after you deploy the application.
Canceling a Deployment
While a deployment is in progress, you can cancel it by clicking on the "Cancel" button. This will stop the deployment process and revert the application to its previous state.
History and Rollback
The "History" card provides an audit trail for deployment events and cron job runs of this service. You can drill down to logs of a particular event by clicking on the logs icon.
Configuration diff
Kapstan maintains a full history of configuration changes done per deployment event. You can view the configuration diff between any newer deployment events and this event by clicking on the 
icon on that event.
Rollback
To rollback to a previously deployed state, click the 
button on that event row, review the configuration diff and deploy.
- If this service is referencing a shared environment variable, then the latest value of shared variable will continue to be used irrespective of which version you deploy. Shared variables work on the concept of reference, and hence a point in time value is not considered.
- Service connections cannot be reverted as part of configuration rollback. Service connections and injected variables will be available as per the latest configuration. In order to remove a connection, it will have to be explicitly done .
- The rollback will fail if any dependencies that are required by that version do not exist anymore. For example:
- The desired configuration may be referencing a shared variable that does not exist anymore.
- The desired configuration may be relying on a certificate that has been deleted.
