Just a big shoutout to #Ansible and #AWX for being able to manage a AWX instance using Ansible.
The instance is running in #Kubernetes, managed by #ArgoCD. But the inner configuration of AWX (LDAP, Teams, Organisations, Permissions, Templates, Projects, Inventories, Credentials) needs to be managed,too. That is where Ansible comes in.
Next week I will once again have a AWX instance that manages itself by running a job on AWX. Nice, eh?
@johanneskastl I've been trying to push for this kind of workflow in work for a long time. We've been maintaining playbook setups across multiple AWX instances manually and it's such a pain. It's so easy for someone to make a change when troubleshooting and then forget to revert it, or worse, to apply it to other envs...
We only recently got access to make API tokens so we could use Ansible to maintain our setups but for some reason the RBAC side of things hasn't caught up and our tokens can create objects but not update them... Sometimes AWX frustrates me no end