automation-api-quickstart

automation-api-quickstart copied to clipboard

I'm struggling to work out how the approach will allow for failover of the Control-M Server, as the communication is initiated by the Control-M agent as a persistent connection, how...

BarrinMW

decommission_controlm.sh and run_register_controlm.sh fail if active jobs use hostgroup/agent alias. The api will not let the agent alias be deleted if it is the same as the previous container's agent...

boogerburns

I suppose that the environment for the ctm cli is not really explicitly needed, as there should be only one in the container, but if a workload created and activated...

dcompane

Hi, It will be nice if your Automation-API could respect Open Service Broker API (https://www.openservicebrokerapi.org/) to have the capacity to incude Control-M directly in solution like CloudFoundry and Kubernetes. I...

bigloupe

Is there a way to automate adding remote host using a predefined ssh key stored in the controlm server? Currently I couldn't use the add remotehost api using the ssh...

balchua

Hi, I have a question. The document states that it has been tested in the EKS V1.20 environment and that additional drivers must be installed when configured in EKS V1.23....

Redkog

Folloing 301, I have finish to generate a image for Control-M/Agent. while running the step 3 : "kubectl apply -f stateful_ha.yaml" persistentvolumeclaim/ha-agent-pvc unchanged statefulset.apps/ha-statefulset-agent unchanged The messages as below: [controlm@km...

deathhoung