Skip to content
View as markdown Ask ChatGPT Ask Claude

Undeploy Automation Manager#

🔒 AutomationManager.Undeploy

Overview#

This operation is used to undeploy an existing Automation Manager.

Setup#

No specific setup is required other than to meet the preconditions of the transaction.

Warning

If there is an existing Persistent Volume Claim (PVC) for a Persistent Volume (PV), undeploying the Automation Manager may fail to release the PVC due to insufficient permissions, and as a result, the PV cannot be reused.

Preconditions#

  • The Automation Manager exists in the system.
  • The Automation Manager has the Deployment Mode set as AutomaticDeploy.
  • The Automation Manager has the Deployment State set as Ready.

Sequence of Steps#

  1. Select Undeploy to perform the operation. The current Deployment State will be changed to Setup.

Deployment Token#

Undeploying an Automation Manager revokes the Personal Access Token (PAT) that the Automation Manager Controller issued for it and clears the UserName and UserAccount entries of the deployment configuration. The Kubernetes secret that stores the token is deleted together with the Deployment of the Automation Manager. The next deploy selects the integration user again and issues a new token. For more information, see Deploy Automation Manager.

Note

Only tokens named AMC-<timestamp>-<automation manager id> and secrets named am-user-<user account>-token-<automation manager id> are removed.