Skip to content

Conversation

stenio123
Copy link
Contributor

Previously, Vault secret engines were called "secret backends". Since then this naming convention has changed, and most docs have been updated.

In this PR I just update the page for the Nomad secret engine, which used the outdated terminology.

@stenio123 stenio123 added the docs label May 6, 2020
The first step to using the vault backend is to mount it.
Unlike the `generic` backend, the `nomad` backend is not mounted by default.
The first step to using the secret engine is to mount it.
Unlike the `cubbyhole` secret engine, the `nomad` secret engine is not mounted by default.
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think the cubbyhole secret engine is mounted by default is it?

Copy link

Choose a reason for hiding this comment

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

Yep totally, and you can't disable.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hello!
I have vault 1.4.0 +ent and ran with

vault server -log-level=trace -dev -dev-root-token-id=root -dev-listen-address=127.0.0.1:8200 \

The two default secret engines mounted are cubbyhole and secret (kv v2). I was just trying to make the least amount of changes while updating the content. I think back in the day the default mount was named "generic".

Please advise if you would prefer something else.

@aphorise
Copy link
Contributor

aphorise commented Aug 15, 2022

What's the status with this request - the terminology does still require correction since secret backend is now deprecated and there's the CLI / commands in the docs that also needs correction.

@aphorise
Copy link
Contributor

@brianshumate @yhyakuna - would appreciate your input here and weather an additional PR maybe needed for CLI / commands in the docs too.

@yhyakuna
Copy link
Contributor

Track this fixes with PR 16859, so closing this old PR.

@yhyakuna yhyakuna closed this Aug 24, 2022
sapk pushed a commit to sapk-fork/vault that referenced this pull request Aug 27, 2025
…ed changelogs as enterprise only files (hashicorp#8906) (hashicorp#8938) (hashicorp#8944)

Don't categorize changelog files that begin with an underscore as
enterprise only, otherwise they'll be removed when backporting changes
to CE.

Since we want to include links to commit SHAs in the changelog we have
to create the changelog in the context of CE and thus need to backport
all of those changes.

We also fix a few Go tests that hand not been updated to handle the
updated default inactive CE groups.

Signed-off-by: Ryan Cragun <[email protected]>
Co-authored-by: Ryan Cragun <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants