101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

480
active users

#awx

0 posts0 participants0 posts today

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: ansible.readthedocs.io/project
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)

ansible.readthedocs.io12. Secret Management System — Ansible AWX community documentation

Anyone with Ansible/AWX experience accessing HTTP APIs on protected networks?

I have tried documentation, the global web and chat with colleagues. Time to bring on the fedi human search.

Using ansible on switches that require you to come from a protected network is easy, you set up your ssh command to go through a jumphost. Accessing switches or firewalls that use an HTTP API is easy, you use a package that talks to the HTTP API, probably using the httpapi package.

But an HTTP API where you need to come from a protected network? Manually it's easy, just `ssh -D` to a jumphost/bastion in the right network and tell curl to use a SOCKS proxy.

On the Ansible side though, I can't find the right place to get httpapi to go through a SOCKS proxy, and I'm not sure where's the best place to run that ssh command.

Has anyone on Fedi already solved this problem?

#k3s and #awx upgraded in my homelab :awesome: but then I spent like 1 hour debugging, why awx cant reach internet and all DNS were responding my public IP.. found that it was going to “google.com.my.domain.com” and that was responding with my ip address as I have dns record with “my.domain.com” towards my public IP. Removed my.domain.com from search in resolv.conf, scale down / up pods and everything was working again :ablobcatreach: #homelab #selfhosting

Spent quite a bit of time today resolving issues in #NetBox, custom #Ansible #Python inventory code, and #AWX. It's very interesting what's involved in turning a series of playbooks into a collection, and separating the inventory into a separate component of AWX, along with fighting #Kubernetes to ensure it allocates enough pod resources so it doesn't go "out of memory" when generating a big inventory.

📯 The Bullhorn 130
#Ansible #Community #newsletter

Releases:
- antsibull 0.60.0
- antsibull-changelog 0.25.0
- #AWX 23.8.1
- AWX Operator 2.12.1

Updated collections:
- amazon.aws
- kubernetes.core
- ibm.ibm_zos_core
- community.postgresql
- community.clickhouse

Collections to be removed:
- purestorage.fusion
- netapp.storagegrid
- community.rabbitmq

Events/meetups in:
- Frankfurt
- Singapore
- Zürich

More:
- Ansible 9 changelog in Markdown
- Spotter playground

➡️ mailchi.mp/redhat/the-bullhorn

📯 The Bullhorn 129
#Ansible #Community #newsletter

Events:
- #FOSDEM + #Cfgmgmtcamp + #AnsibleCollab STARTING TODAY
- Ansible Anwendertreffen

Releases:
- Ansible 9.2.0
- #AWX 23.7.0
- AWX Operator 2.11.0
- ansible-core 2.14.14, 2.15.9 & 2.16.3

Collections:
- community.general 8.3.0
- community.docker 3.7.0
- community.dns 2.8.0
- community.clickhouse 0.2.0
- community.routeros stable-1 EOL
- community.dns stable-1 EOL
- inspur.sm unmaintained

Hop hop ➡️ mailchi.mp/redhat/the-bullhorn

📯 The Bullhorn 119
#Ansible #Community #newsletter

News:
- Execution environments docs update
- EE images available
- Ansible Contributor Summit (register now!)

Releases:
- antsibull-docs 2.5.0
- Ansible 9.0.0 Alpha2
- ansible-core 2.16.0b2

Project updates:
- #AWX Google Group moving to Ansible Community Forum
- topics & recordings from Aug/Sep AWX office hours

More fun:
- #Hacktoberfest! 🍻
- Burning servers?! 🔥
- meetups in Buenos Aires, Colorado, and Atlanta 🗺️

➡️ mailchi.mp/redhat/the-bullhorn