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: add a note on ? and : in operators.mdx into v1.9 #35804

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 2, 2024

Backport

This PR is auto-generated from #35802 to be assessed for backporting due to the inclusion of the label 1.9-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:
@crw
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: "fcf1f6d647ed8e185cf576a22a2902127ff0de7e", automatic backport requires rebase workflow

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


Adds a note clarifying that the ? symbol is not considered a standalone operator in Terraform. Instead, it is part of the conditional expression syntax when combined with :.

Fixes #35799


Overview of commits

@crw crw marked this pull request as ready for review October 2, 2024 23:25
@crw crw closed this Oct 2, 2024
@crw crw deleted the backport/call-out-ternary-operator/seriously-funky-sawfly branch October 2, 2024 23:26
Copy link
Contributor Author

github-actions bot commented Nov 2, 2024

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants