Description:

When a template with this option runs, the job runs a "while true loop" process on the target nodes. When the job is done the process ends. Any job triggered by AAP first looks for this "locked" process, and if found, AAP waits a pre-defined amount of time before starting this job (the value needs to be configurable in the UI).

This is just a simple example from the customer. They also want to ensure that a feature is included that makes the option AAP "instance-agnostic" so that it does not matter from which instance the job originated because there are several different instances that are not aware of one another.

I have attached example.png of what the customer thinks this feature could look like.

Phil Griffiths agreed that this feature is a potential "Policy as Code" use case (a feature eventually coming down the pipeline) and would need to be categorized as such.

Business Impact:

This would greatly enhance the customer's workflow because they could have templates that are allowed to run while other jobs are running and ones that are not allowed. To use a patching example, they would want the "job lock" option to be an intelligent way for nodes to avoid potentially conflicting job types, i.e., they do not want target nodes trying to run an upgrade job while a patch job is running.