I've spent the morning to include a patch into a home-made debian package for the Ansible awx.awx collection. My patch[1] is not yet merged upstream so I had to backport to the version we use.

The latest version of AWX has been released more than a year ago. Is the project dead?

[1] https://github.com/ansible/awx/pull/15988

I found Squest (https://github.com/HewlettPackard/squest/) recently, which is a self-service portal built on top of #AWX #RedHat #AAP (Ansible Automation Platform). Of course I had to try this out...

@christianhuth put together a Helm chart, while I tried to get upstream's way of deploying to work (they are using an #Ansible playbook-role construct to install this into #Kubernetes).

Here is the first result, the helm-based #vagrant #libvirt setup:
https://codeberg.org/johanneskastl/squest_on_k3s_vagrant_libvirt_ansible
https://github.com/johanneskastl/squest_on_k3s_vagrant_libvirt_ansible

(The ansible branch using upstream's deployment will follow, once I get it working with vagrant-libvirt...)

Have a lot of fun!

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?

Dear #AWX users out there (AWX as in Ansible, not AWS as in Amazon...),

does anyone have good pointers on connecting AWX and #Hashicorp #Vault / #OpenBoa **without** having to define each secret/credential again in AWX?

I have set up a basic connection according to the documentation: https://ansible.readthedocs.io/projects/awx/en/24.6.1/userguide/credential_plugins.html#ug-credentials-hashivault
And I have created a credential using that lookup and could successfully output its value in a playbook run in AWX.

But having to define a AWX credential for each secret that I need to pull from Vault/OpenBoa sounds like a lot of unnecessary duplication.
(Yes, I know you can manage AWX via Ansible. We do that already. But still, you need to define the credentials in your code somewhere for the automation to create it in AWX)

Hab heute Ansible OpenSource version AWX installiert. Siehe da es lief fast auf Anhieb ohne Fehler.

Low temperatures Saturday night/Sunday morning in and around Alaska. Most areas near to a bit above normal. #awx #weather