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 terraform test: run block names should be valid HCL identifiers into v1.7 #34470

Merged

Conversation

teamterraform
Copy link
Contributor

Backport

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

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


Validate that run block names are valid HCL identifiers when they are parsed instead of failing with obscure error messages later.

Fixes #34372

Target Release

1.7.0

Draft CHANGELOG entry

BUG FIXES

  • terraform test: Improve error message for invalid run block names.

Overview of commits

@teamterraform teamterraform force-pushed the backport/liamcervante/34372/grossly-engaging-ibex branch from 47cad2a to 5ec929f Compare January 3, 2024 12:03
@liamcervante liamcervante merged commit 5ef9e61 into v1.7 Jan 3, 2024
6 checks passed
@liamcervante liamcervante deleted the backport/liamcervante/34372/grossly-engaging-ibex branch January 3, 2024 12:13
Copy link
Contributor

github-actions bot commented Jan 3, 2024

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

Copy link
Contributor

github-actions bot commented Feb 3, 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 Feb 3, 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