...
- ACM in UNINITIALIZED state: all elements of a ACM are in UNINITIALIZED state, all applications are not deployed and policy types are not deployed and not present in Api.
- User trigger triggers to move ACM from UNINITIALIZED to PASSIVE: all elements of a ACM are in UNINITIALIZED_TO_PASSIVE, all applications are getting deployed and configured, and policy types are getting created in Api and deployed with Pap.
- Element in PASSIVE state:
- ks8: application is deployed.
- policy: a policy type is create in Api and deployed with Pap.
- http: application is configured.
- ACM in PASSIVE state: all applications are deployed and configured.
- User trigger triggers to move ACM from PASSIVE to UNINITIALIZED: all elements of a ACM are in PASSIVE_TO_UNINITIALIZED, all applications are getting undeployed, and policy types are undeployed with Pap and delete in Api.
...
- ACM in UNINITIALIZED state: all elements of a ACM are in UNINITIALIZED state, all applications are not deployed and policy types are not deployed and not present in Api.
- User trigger triggers to move ACM from UNINITIALIZED to RUNNING: all elements of a ACM are in UNINITIALIZED_TO_PASSIVE, all applications are getting deployed and policy types are getting created in Api and deployed with Pap.
- ACM in UNINITIALIZED_TO_PASSIVE_ERROR state: got error during deploy.
- Element in PASSIVE state: application is deployed or a policy type is create in Api and deployed with Pap.
- ACM in PASSIVE state: applications are deployed, but not configured yet. In this state, runtime-ACM triggers elements in state PASSIVE_TO_RUNNING.
- Element in PASSIVE_TO_RUNNING: applications are getting configured.
- ACM in PASSIVE_TO_RUNNING_ERROR state: error during configuration.
- ACM in RUNNING state: all elements of a ACM are in RUNNING state, all applications are running.
...