Skip to content
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

Backport of Typo: Corrected same typo in 2 locations (on-premise to on-premises) into stable-website #13945

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #13402 to be assessed for backporting due to the inclusion of the label backport/website.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

The below text is copied from the body of the original PR.


what it accomplishes: "on-premise" should be "on-premises", since "premise" has a different meaning
how it does so: modified 2 files in the website folder

digivava and others added 30 commits November 17, 2021 19:52
* post 1-9 doc changes

* fixed endpoint sample

* Update website/content/docs/release-notes/1.9.0.mdx

Co-authored-by: Yoko Hyakuna <[email protected]>

Co-authored-by: Yoko Hyakuna <[email protected]>
Moved from one of the first items in the navbar down to one of the last. They are not high priority information and should be grouped with upgrade and release notes.
* change default vaule for disable_iss_validation to be true

* mark as deprecated | remove issuer from sample

* deprecation section

* additional informaiton about when fields will be removed

* additional deprecation note under csi provider

* punctuation

* make the deprecation note more noticable

* missing issuer sentence | remove whitespace

* Update website/content/docs/platform/k8s/csi/index.mdx

Co-authored-by: Ben Ash <[email protected]>

* cleanup

* additional deprecation comments

* fix discovery link

* highlight

* no need to configure the issuer

Co-authored-by: Ben Ash <[email protected]>
* incorporated feedback

* fixed link

* fixed link again

* found another error
* README.md of website/ with WARNING on rebuilding

* Update README.md
* adding custom_metadata read and update changes

* adding custom metadata changes
* Update Vault Agent intro

* Update website/content/docs/agent/index.mdx

Co-authored-by: Brian Shumate <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Brian Shumate <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Brian Shumate <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

* Update website/content/docs/agent/index.mdx

Co-authored-by: Loann Le <[email protected]>

Co-authored-by: Brian Shumate <[email protected]>
Co-authored-by: Loann Le <[email protected]>
* update custom headers to mention 1.9 is required

Per https://github.com/hashicorp/vault/blob/main/CHANGELOG.md#190-rc1 the custom response headers are a new feature introduced in 1.9, meaning we should explicitly call out this version requirement in documentation, otherwise users of earlier versions of Vault will unable to use the functionality and may consider it a bug.

* Update website/content/docs/configuration/listener/tcp.mdx

reads better, agreed

Co-authored-by: Loann Le <[email protected]>

Co-authored-by: Loann Le <[email protected]>
A few sidebar elements are hidden for unknown reasons. If we have a
reason to keep them hidden (vs deleting the element and associated docs),
maybe we could add `"_comment":"Hidden because ..."` to them.

A few other elements were definitely obsolete so I've removed them.
path-help.mdx is now the reference for help.
* modified based on feedback

* Update faq.mdx

fixed text
* website: fix print styles by bumping deps

* website: remove old highlight js prints style code

* fix: hashi-stack-menu selector
Currently the example given results in 2.3.4.5 if it is indexed from other side. This new example prevents confusion because it is now clear which side x_forwarded_for_hop_skips is indexing from
* Rework 1.21 content into one heading and add note at top
* Add notes about extended k8s token duration
* Add example of ClusterRoleBinding for using client JWTs
* Add entity-alias behavior change to docs

* Add upgrade note about entity-alias mapping change

* Rename 1.7-9 upgrade pages, shuffle upgrade note position

* Update website/content/partials/entity-alias-mapping.mdx

Co-authored-by: Meggie <[email protected]>

* Add incorrect policy issue to the docs

* Add example about entity-alias restriction

Co-authored-by: Meggie <[email protected]>
This pull request was automerged via backport-assistant
…into stable-website (#13826)

This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
…to stable-website (#13845)

This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
…website (#13861)

This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
…13596)

* backport of commit 3e64bca

* backport of commit 9b97cb7

* backport of commit 2cb8b77

* backport of commit dc66009

* backport of commit e00c4b0

* backport of commit 7576a43

Co-authored-by: tvsaru <[email protected]>
Co-authored-by: Loann Le <[email protected]>
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
This pull request was automerged via backport-assistant
…ebsite (#13928)

This pull request was automerged via backport-assistant
…o stable-website (#13932)

This pull request was automerged via backport-assistant
@hashicorp-cla
Copy link

hashicorp-cla commented Feb 8, 2022

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


2 out of 3 committers have signed the CLA.

  • hc-github-team-secure-vault-core
  • schavis
  • temp

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

@vercel vercel bot temporarily deployed to Preview – vault-storybook February 8, 2022 00:00 Inactive
@vercel vercel bot temporarily deployed to Preview – vault February 8, 2022 00:02 Inactive
@VioletHynes VioletHynes added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jul 6, 2023
…cs/typo-premise-to-premises/horribly-worthy-cattle
@schavis schavis merged commit 6bfbb0d into stable-website Aug 16, 2023
@schavis schavis deleted the backport/docs/typo-premise-to-premises/horribly-worthy-cattle branch August 16, 2023 20:57
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.