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 docs: azurerm backend updates for 1.11 release into v1.11 #36699

Conversation

github-actions[bot]
Copy link
Contributor

Backport

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

🚨

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:
@dbanck
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: unable to process merge commit: "800db2d5a6ddf1d65b096ca7cf3c8b92419e9768", automatic backport requires rebase workflow

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


This PR is to update the azurerm backend docs for correctness following the 1.11 release.

Related: #36623

Target Release

1.11.1

CHANGELOG entry

  • This change is user-facing and I added a changelog entry.
  • This change is not user-facing.

Overview of commits

@github-actions github-actions bot force-pushed the backport/docs/azurerm-backend-1-11-updates/certainly-helping-hare branch from 9503790 to d8eb0cb Compare March 14, 2025 16:00
@github-actions github-actions bot requested a review from dbanck March 14, 2025 16:00
@dbanck
Copy link
Member

dbanck commented Mar 14, 2025

Closed in favor of #36700

@dbanck dbanck closed this Mar 14, 2025
@dbanck dbanck deleted the backport/docs/azurerm-backend-1-11-updates/certainly-helping-hare branch March 14, 2025 16:04
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.

2 participants