The LMI uses a two-stage commit process when you make changes to the appliance.
Multiple changes can exist in a pending state at the same time. They are committed or rolled back together when a user deploys or rolls back these changes.
Any changes that affect running reverse proxy instances require a restart of the effected instances before the changes can take effect.
If there are conflicts between the pending changes and the production files, then all pending changes are automatically rolled back and the production files remain unchanged.
https://{appliance_hostname}/pending_changes/deploy
GET
HTTP response code and JSON error response where applicable.
Request:
GET https://{appliance_hostname}/pending_changes/deploy
Response:
200 ok
https://{appliance_hostname}/pending_changes/forget
GET
HTTP response code and JSON error response where applicable.
Request:
GET https://{appliance_hostname}/pending_changes/forget
Response:
200 ok
https://{appliance_hostname}/pending_changes/count
GET
HTTP response code and JSON data that represents the number of pending changes.
Request:
GET https://{appliance_hostname}/pending_changes/count
Response:
{"count": 3}
https://{appliance_hostname}/pending_changes
GET
HTTP response code and JSON data that represents the list of pending changes.
Request:
GET https://{appliance_hostname}/pending_changes
Response:
200 ok
[{
"id": 0,
"policy": "SSL Certificates",
"user": "admin",
"date": "2012-11-05T11:22:20+10:00"
}]
When there are pending changes, a warning message is displayed at the top of the main pane. To deploy or roll back the pending changes: