Skip to content

Conversation

@kiran-4444
Copy link

Description

What does this PR do?

This PR adds the ability to view secrets as YAML. The design is minimal and was implemented to see the expected behaviour. I need help in polishing this further.

Fixes #29481

TODO only if you're a HashiCorp employee

  • Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
    • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    of a public function, even if that change is in a CE file, double check that
    applying the patch for this PR to the ENT repo and running tests doesn't
    break any tests. Sometimes ENT only tests rely on public functions in CE
    files.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

@kiran-4444 kiran-4444 requested a review from a team as a code owner May 6, 2025 19:31
@hashicorp-cla-app
Copy link

hashicorp-cla-app bot commented May 6, 2025

CLA assistant check
All committers have signed the CLA.

@kiran-4444
Copy link
Author

@heatherezell Can you take a look at this? Thanks!

@Monkeychip
Copy link
Contributor

@kiran-4444 thank you so much for the PR. The KV secrets engine is widely used, and any feature we add has to go through a longer design process. I have surfaced this PR to design, but there is no larger need for this feature at the moment.

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.

UI: Add the ability to display the secret as YAML

3 participants