What is the nature and description of the request?

Operator-based deployments of AAP require a number of context switches between the terminal and AAP in order to configure an automation mesh node. While the current process of 1) configure the instance, 2) download the bundle, 3) run the bundle is functional, it can be improved to help overcome customer burden in order to complete the configuration. The existing experience should remain for disconnected environments, but automation controller should have a model for running the configuration bundle from within controller itself so that when you configure an instance node, then controller will run the playbook to configure the node all from within the AAP experience. The user could have two options from controller, 1) configure node (which would run the playbook from controller with the required settings to connect to the instance), or 2) download bundle for instances where deeper configuration is required.

Why does the customer need this? (List the business requirements here)

The current automation mesh configuration experience requires a number of steps that can be automated by AAP. We place a burden on customers to run a playbook manually to configure these mesh nodes, but AAP can run those jobs directly, which improves user experience and limits the need to drop to the shell for AAP configuration steps.

How would you like to achieve this? (List the functional requirements here)

• Instance configuration in automation controller can auto-run the generated bundle for an automation mesh node if that mesh node is routable by AAP and has a configured credential. During mesh setup, the process would include attaching a machine credential to allow for running the automation in AAP.

List any affected known dependencies: Doc, UI etc..

• Docs would need to be updated to account for the additional capability