fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

9.8K
active users

#HashiCorp

1 post1 participant1 post today

....aaaaaand #OpenBao (the fork of #Hashicorp #Vault) is on its way to @opensuse #Tumbleweed in the latest version 2.2.1. Since 2.2.0 the webui is included in OpenBao, so this can be a full replacement for Vault!

Looking forward to doing more testing with it!

In case you want to try it out, here is a #vagrant #libvirt setup using #Ansible to prepare an OpenBao server VM and a client using a secret.
codeberg.org/johanneskastl/ope

Summary card of repository johanneskastl/openbao_vagrant_libvirt_ansible
Codeberg.orgopenbao_vagrant_libvirt_ansibleVagrant-libvirt setup with an OpenBao Server and a client VM running the OpenBao Agent (and a PostgreSQL database)

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

I'm excited to announce that I've been selected as a HashiCorp Ambassador for 2025.

Our journey with HashiCorp started early on with Vagrant to simplify project virtualization. In 2019, we chose Nomad over Kubernetes for its simplicity and scalability. Last year, we implemented Boundary & Vault for simple and secure remote access based on user identity.

If you want to know more about Nomad or Boundary, let me know.

Uuuuuuuh, #OpenBao (the open source fork of #Hashicorp #Vault) just released version 2.2.0 and now includes the UI, that was missing so far.

The package for @opensuse was adapted, tested and worked out fine. Will soon be available in #Tumbleweed!

If you want to test this out, feel free to use this vagrant-libvirt setup of mine:
codeberg.org/johanneskastl/ope

Summary card of repository johanneskastl/openbao_vagrant_libvirt_ansible
Codeberg.orgopenbao_vagrant_libvirt_ansibleVagrant-libvirt setup with an OpenBao Server and a client VM running the OpenBao Agent (and a PostgreSQL database)