Hussain, we spoked earlier in the. booth. The pipeline creates the Change Request automatically and is blocked until a decision has been made (approval or reject). We use a callback to avoid an active expensive looping

In addition since it’s an asynchronous api call we are not going to time out like an open tcp session would.

Cool, thank you both for the insight. I am looking to setup something similar with Ansible Tower to do prod deployements. Similar to Jenkins , Tower creates a CHG and needs to wait to proceed further based on approval.

Look into our OOTB ansible Integration in Cloud Provisioning and Governance module

That includes the ability to consume and call Tower actions and create/automate with changes all within day 2 ops framework for cloud users to consume self-service

Sure, will take a look at it. We have implemented GitOps framework, where the user updates the code in GIT and changes are deployed to all regions via Tower webhook.

Using ServiceNow piece for recording those via Standard change

What no Jenkins? No ADO? Using existing Ansible infra. Crazy times.