Login

Recent searches

No recent searches

Search options

Only available when logged in.
social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

487
active users

social.coop: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#openboa

1 post1 participant0 posts today
Johannes Kastl<p>Dear <a href="https://digitalcourage.social/tags/AWX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AWX</span></a> users out there (AWX as in Ansible, not AWS as in Amazon...),</p><p>does anyone have good pointers on connecting AWX and <a href="https://digitalcourage.social/tags/Hashicorp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Hashicorp</span></a> <a href="https://digitalcourage.social/tags/Vault" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Vault</span></a> / <a href="https://digitalcourage.social/tags/OpenBoa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenBoa</span></a> **without** having to define each secret/credential again in AWX?</p><p>I have set up a basic connection according to the documentation: <a href="https://ansible.readthedocs.io/projects/awx/en/24.6.1/userguide/credential_plugins.html#ug-credentials-hashivault" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ansible.readthedocs.io/project</span><span class="invisible">s/awx/en/24.6.1/userguide/credential_plugins.html#ug-credentials-hashivault</span></a><br>And I have created a credential using that lookup and could successfully output its value in a playbook run in AWX.</p><p>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.<br>(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)</p><p><a href="https://digitalcourage.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DevOps</span></a> <a href="https://digitalcourage.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a> <a href="https://digitalcourage.social/tags/InfrastructureAsCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InfrastructureAsCode</span></a> <a href="https://digitalcourage.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ansible</span></a></p>
Ric Harvey 🇪🇺🌍💚<p>When <a href="https://awscommunity.social/tags/IBM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IBM</span></a> created the fork of <a href="https://awscommunity.social/tags/HashiCorp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HashiCorp</span></a> <a href="https://awscommunity.social/tags/vault" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vault</span></a> they missed the chance to call it openSesame allowing people to open it and give them all the secrets. I’m disappointed to say the least. <a href="https://awscommunity.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> <a href="https://awscommunity.social/tags/openboa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>openboa</span></a></p>
ExploreLive feeds
About