1. Go to Templates and create a Workflow Template.
2. Add multiple job templates in a sequential or conditional order.
Explanation:
Workflow templates orchestrate complex automation sequences, enabling multi-step operations in a single execution.

# host_vars/web1.yml
ansible_ssh_private_key_file: ~/.ssh/web1_key
Explanation:
Defining ansible_ssh_private_key_file ensures secure, host-specific authentication, vital for multi-host environments.

1. Launch a job template using the EE.
2. Check the job output logs for the EE image used:
o Look for: Using Execution Environment: registry.example.com/my_execution_env:latest.
Explanation:
Validating the EE ensures that the job uses the correct runtime with the required dependencies.

git config --global user.name "Developer"
git config --global user.email "[email protected]"
Explanation:
Configuring a username and email ensures commits are properly attributed to the user in version history.

1. Go to the project in Automation Controller.
2. Click Sync and monitor for errors.
Explanation:
Syncing tests whether Automation Controller can connect to the repository and fetch content without issues.