Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

replace Vault with OpenBao in documentation #44

Merged
merged 2 commits into from
Jan 22, 2024

Conversation

JanMa
Copy link
Member

@JanMa JanMa commented Jan 12, 2024

This replaces vault with openbao in the documentation where I think it makes sense. As with the API docs, I left references to older Vault versions and the Enterprise offering in tact. I also did not change any API responses or X-Vault HTTP headers.

Sorry in advance for the huge PR :-)

@joewxboy joewxboy self-requested a review January 18, 2024 16:49
@cipherboy
Copy link
Member

Will take a look at this when I get back!

Copy link
Contributor

@joewxboy joewxboy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In summary ...

  1. Filenames and paths likely use either "openbao" or just "bao" but let's confirrm with the development team. These include cacert, binpath, config, token, and logfiles.
  2. The hostname is either "openbao-fqdn" or just "bao-fqdn" but I don't know which. Please confirm.
  3. The CLI (or shell) is definitely just "bao" and not "openbao". Please change all instances.
  4. Let's NOT change the documentation page filenames and paths just yet. Let's handle that in a separate change. This would also include the section IDs, which appear in the URL past the hash sign (#).
  5. Let's confirm the service name, display name, and registry key, both to ensure it is "openbao" and not "bao" but also to confirm the case.

cipherboy pushed a commit to cipherboy/openbao that referenced this pull request Jan 21, 2024
Co-authored-by: hc-github-team-secure-vault-ecosystem <hc-github-team-secure-vault-ecosystem@users.noreply.github.com>
Co-authored-by: Max Coulombe <109547106+maxcoulombe@users.noreply.github.com>
@JanMa JanMa force-pushed the sanitize-docs branch 3 times, most recently from 3fdc236 to 1de915d Compare January 21, 2024 20:17
Copy link
Contributor

@joewxboy joewxboy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two items to address in a separate (future) GitHub issue:

  1. Style guide to address whether "server", "token", "agent", "proxy" should be capitalized when used as a proper name, such as "OpenBao Agent". The documentation is currently inconsistent in usage.

  2. Ensure all GitHub repo path references are correct.

Signed-off-by: Jan Martens <jan@martens.eu.org>
Signed-off-by: Jan Martens <jan@martens.eu.org>
@naphelps naphelps requested review from naphelps and removed request for cipherboy January 22, 2024 15:18
@naphelps naphelps merged commit bc22cd1 into openbao:development Jan 22, 2024
7 of 9 checks passed
Copy link
Member

@cipherboy cipherboy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow, a lot of really good content here! Thank you @JanMa for your attention to detail :-)

@@ -34,7 +34,7 @@
},

{
"title": "Installing Vault",
"title": "Installing Openbao",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not to nitpick, but we might want to make these consistent in the future.

well.

Vault upgrades are designed such that large jumps (ie 1.3.10 -> 1.7.x) are
OpenBao upgrades are designed such that large jumps (ie 1.3.10 -> 1.7.x) are
Copy link
Member

@cipherboy cipherboy Jan 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may want to revisit this in the future as a community, to see if we wish to keep this upgrade mechanism or not.

The Google Cloud KMS secrets engine for Vault interfaces with Google Cloud
KMS for encryption/decryption of data and KMS key management through Vault.
The Google Cloud KMS secrets engine for OpenBao interfaces with Google Cloud
KMS for encryption/decryption of data and KMS key management through OpenBao.
---

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JanMa This one is also an Enterprise secret engine iirc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants