Recently we merged the last of the transactional storage pull requests, including PostgreSQL support!

I'm pleased to announce that our first direction and roadmap document has been approved by the TSC!

This represents a major commitment to openness for this project. Historically, upstream hasn't published an open roadmap or collaborated with the community on a shared vision and direction for their project.

\o Hello OpenBao community!

In our last community post, we said:

Join the community and its leadership today.

But you said: it is not clear how!

Good news: Our community roles are approved and live!

OpenBao and upstream lack server-side cross-pluign communication.

As recently seen with an OIDC feature, this shortcoming often needs to be worked around on the client side, potentially exposing sensitive information.

There's usually two paths discussed for cross-plugin communication:

1. Requests bound under the context of the original user token.
2. Designing some other authorization system or an internal API based design.

We asked one of our Gen Z community members to describe OpenBao recently. They wrote the following:

We are thrilled to announce the availability of OpenBao v2.0.0, its initial GA release!

It was fabulous to see contributors and member companies from a wide range of backgrounds come together to support OpenBao over the past several months and build an initial GA release in the open. This release focuses mostly on stabilizing the fork, reducing the binary size, and giving the community room to make the decisions it needs to ensure a healthy start to the ecosystem.