Skip to content

Backport of [release/1.15.3] Add cloud stanza documentation into release/1.14.x#17352

Closed
hc-github-team-consul-core wants to merge 1 commit intorelease/1.14.xfrom
backport/jer/cloud-docs/briefly-adequate-filly
Closed

Backport of [release/1.15.3] Add cloud stanza documentation into release/1.14.x#17352
hc-github-team-consul-core wants to merge 1 commit intorelease/1.14.xfrom
backport/jer/cloud-docs/briefly-adequate-filly

Conversation

@hc-github-team-consul-core
Copy link
Collaborator

Backport

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

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@hanshasselberg
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul/merges: 409 Merge conflict []

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


Description

This PR adds documentation for the HCP cloud stanza.

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/jer/cloud-docs/briefly-adequate-filly branch from 74fe2be to f903259 Compare May 15, 2023 10:53
@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/jer/cloud-docs/briefly-adequate-filly branch from f903259 to 74fe2be Compare May 15, 2023 10:53
@hashicorp-cla
Copy link

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


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.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Auto approved Consul Bot automated PR

@vercel vercel bot temporarily deployed to Preview – consul May 15, 2023 10:58 Inactive
@vercel vercel bot temporarily deployed to Preview – consul-ui-staging May 15, 2023 10:58 Inactive
@github-actions github-actions bot deleted the backport/jer/cloud-docs/briefly-adequate-filly branch August 29, 2025 06:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants