Skip to content

Update README#31244

Merged
schavis merged 7 commits into
mainfrom
et/add-readme-docs-of-move-to-udr
Jul 22, 2025
Merged

Update README#31244
schavis merged 7 commits into
mainfrom
et/add-readme-docs-of-move-to-udr

Conversation

@Younique98
Copy link
Copy Markdown
Contributor

@Younique98 Younique98 commented Jul 10, 2025

Let contributors know that docs will now be located in UDR

Description

What does this PR do?
Inform contributors that docs will now be located in UDR going forward

Asana Ticket

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.

PCI review checklist

  • [ x] I have documented a clear reason for, and description of, the change I am making.
  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
  • If applicable, I've documented the impact of any changes to security controls.

Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

@Younique98 Younique98 requested a review from a team as a code owner July 10, 2025 16:31
@Younique98 Younique98 requested a review from rmainwork July 10, 2025 16:31
@github-actions github-actions Bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jul 10, 2025
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jul 10, 2025

CI Results:
All Go tests succeeded! ✅

@github-actions
Copy link
Copy Markdown

Build Results:
All builds succeeded! ✅

@Younique98 Younique98 requested review from a team as code owners July 10, 2025 18:28
@Younique98 Younique98 requested review from anwittin and brewgator July 10, 2025 18:28
@Younique98 Younique98 force-pushed the et/add-readme-docs-of-move-to-udr branch from 87b3573 to 9589008 Compare July 11, 2025 14:00
@Younique98 Younique98 added this to the 1.20.1 milestone Jul 11, 2025
@Younique98 Younique98 requested a review from a team as a code owner July 11, 2025 14:13
Comment thread changelog/31244.txt Outdated
Comment thread website/content/api-docs/auth/alicloud.mdx
Comment thread website/content/api-docs/auth/alicloud.mdx
@Younique98 Younique98 removed this from the 1.20.1 milestone Jul 14, 2025
@Younique98 Younique98 force-pushed the et/add-readme-docs-of-move-to-udr branch from b3baabe to 645cf52 Compare July 14, 2025 17:19
@Younique98 Younique98 force-pushed the et/add-readme-docs-of-move-to-udr branch from 645cf52 to 1e3fb72 Compare July 14, 2025 20:47
@Younique98 Younique98 requested a review from VioletHynes July 14, 2025 22:15
rmainwork
rmainwork previously approved these changes Jul 15, 2025
@Younique98 Younique98 force-pushed the et/add-readme-docs-of-move-to-udr branch 3 times, most recently from 99ec360 to 14bc31a Compare July 17, 2025 13:37
Comment thread website/content/docs/deploy/kubernetes/vso/helm.mdx Outdated
@im2nguyen
Copy link
Copy Markdown
Contributor

@Younique98 @schavis should we merge this asap since vault has officially migrated to udr?

Younique98 and others added 7 commits July 22, 2025 08:42
Let contributors know that docs will now be located in UDR
Comment has been added to all mdx docs that are not partials
changelog check failure
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
@Younique98 Younique98 force-pushed the et/add-readme-docs-of-move-to-udr branch from 5c22e82 to 1b10263 Compare July 22, 2025 12:42
@Younique98
Copy link
Copy Markdown
Contributor Author

@im2nguyen Plan on getting it merged in today. Some other things took priority before this :) But will knock it out. Thx!

@Younique98 Younique98 requested review from a team and removed request for a team July 22, 2025 13:54
Copy link
Copy Markdown

@RubenSandwich RubenSandwich left a comment

Choose a reason for hiding this comment

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

👍🏼

@schavis schavis merged commit 0660ea6 into main Jul 22, 2025
33 checks passed
@schavis schavis deleted the et/add-readme-docs-of-move-to-udr branch July 22, 2025 15:12
Erfankam pushed a commit to Erfankam/vault that referenced this pull request Sep 1, 2025
* Update README

Let contributors know that docs will now be located in UDR

* Add comments to each mdx doc

Comment has been added to all mdx docs that are not partials

* chore: added changelog

changelog check failure

* wip: removed changelog

* Fix content errors

* Doc spacing

* Update website/content/docs/deploy/kubernetes/vso/helm.mdx

Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>

---------

Co-authored-by: jonathanfrappier <92055993+jonathanfrappier@users.noreply.github.com>
Co-authored-by: Tu Nguyen <im2nguyen@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 pr/no-milestone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants