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

Add validation to Terraform configuration files used in acceptance tests #37232

Open
gdavison opened this issue May 2, 2024 · 1 comment
Open
Labels
repository Repository modifications; GitHub Actions, developer docs, issue templates, codeowners, changelog.

Comments

@gdavison
Copy link
Contributor

gdavison commented May 2, 2024

Description

The Terraform configurations used in most acceptance tests are defined inline as Go strings, and we use GitHub workflows to validate the formatting and lint the Terraform code. As we move towards Terraform configurations in .tf files using ConfigDirectory, we no longer have these validation steps.

References

Relates #36792

Would you like to implement a fix?

None

@gdavison gdavison added the repository Repository modifications; GitHub Actions, developer docs, issue templates, codeowners, changelog. label May 2, 2024
Copy link

github-actions bot commented May 2, 2024

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
repository Repository modifications; GitHub Actions, developer docs, issue templates, codeowners, changelog.
Projects
None yet
Development

No branches or pull requests

1 participant