8000 VAULT-35385 docs for response_status_code metric by VioletHynes · Pull Request #30396 · hashicorp/vault · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

VAULT-35385 docs for response_status_code metric #30396

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

Merged
merged 2 commits into from
May 13, 2025

Conversation

VioletHynes
Copy link
Contributor
@VioletHynes VioletHynes commented Apr 25, 2025

Description

Docs for #30354

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.

@VioletHynes VioletHynes requested review from a team as code owners April 25, 2025 19:12
@VioletHynes VioletHynes requested a review from JMGoldsmith April 25, 2025 19:12
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Apr 25, 2025
Copy link

CI Results:
All Go tests succeeded! ✅

Copy link

Build Results:
All builds succeeded! ✅

…_status_code.mdx

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
@VioletHynes VioletHynes merged commit 6a19f3a into main May 13, 2025
34 checks passed
@VioletHynes VioletHynes deleted the violethynes/VAULT-35385 branch May 13, 2025 19:03
drivera258 pushed a commit that referenced this pull request May 14, 2025
* VAULT-35385 docs for response_status_code metric

* Update website/content/partials/telemetry-metrics/vault/core/response_status_code.mdx

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>

---------

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
drivera258 pushed a commit that referenced this pull request May 14, 2025
* VAULT-35385 docs for response_status_code metric

* Update website/content/partials/telemetry-metrics/vault/core/response_status_code.mdx

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>

---------

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0