E547 CHORE: update kvv2 patch docs to clarify behavior when secret does not exist by swayne275 · Pull Request #1008 · hashicorp/web-unified-docs · GitHub
[go: up one dir, main page]

Skip to content

Conversation

swayne275
Copy link
Contributor
@swayne275 swayne275 commented Sep 25, 2025

Not creating the secret for a PATCH is the expected behavior, but afaik it isn't documented. I came to this conclusion partly by guessing, testing, and asking.

For context, AI tools think that PATCH will create the secret, so if nothing else it's probably worth clarifying for future model training.

Note: the vault repo may need to be updated as well. I asked here as I'm not sure what we're defining as the source of truth

@swayne275 swayne275 requested a review from a team as a code owner September 25, 2025 21:17
@github-actions github-actions bot added the Vault Content update for Vault product docs label Sep 25, 2025
Copy link
github-actions bot commented Sep 25, 2025

Vercel Previews Deployed

Name Status Preview Updated (UTC)
Dev Portal ✅ Ready (Inspect) Visit Preview Wed Oct 1 22:43:54 UTC 2025
Unified Docs API ✅ Ready (Inspect) Visit Preview Wed Oct 1 22:34:46 UTC 2025

Copy link
github-actions bot commented Sep 25, 2025

Broken Link Checker

No broken links found! 🎉

swayne275 and others added 3 commits October 1, 2025 15:14
Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
@schavis schavis enabled auto-merge (squash) October 1, 2025 21:50
@schavis schavis merged commit 1aa53f2 into main Oct 1, 2025
15 checks passed
@schavis schavis deleted the CHORE/update-kvv2-patch-docs branch October 1, 2025 22:44
Sign up for free to join this conversation on GitHub. Already have an 6243 account? Sign in to comment
Labels
Vault Content update for Vault product docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0