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 cloud: document resource k/v tag usage into v1.10 #35948

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 4, 2024

Backport

This PR is auto-generated from #35942 to be assessed for backporting due to the inclusion of the label 1.10-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:
@brandonc
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: "600848fc93222fc37bac22ca915a8c1457440b58", automatic backport requires rebase workflow

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


Adds supplemental documentation for the usage of key/value tags as an alternative to list of key-only strings in the cloud block

Target Release

1.10.0

Draft CHANGELOG entry

NEW FEATURES

  • cloud: cloud block now allows map of strings to be used as workspace key/value tags

Overview of commits

@radeksimko radeksimko merged commit d9417e9 into v1.10 Nov 13, 2024
6 checks passed
@radeksimko radeksimko deleted the backport/TF-21933-document-cloud-block-tags-behavior-in-1-10/typically-native-catfish branch November 13, 2024 14:38
Copy link
Contributor Author

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

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.

3 participants