You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2024. It is now read-only.
Currently, formatting embedded Terraform code within RST files is a manual process. The proposal is to run a GitHub Actions job in the CI workflow that will automatically format any embedded Terraform code within RST files. Rather than having this job run with every PR, the job should run only if there’s any code change under https://github.com/aiven/devportal/tree/main/docs/tools/terraform
I would recommend we move the code out to terraform files and format those correctly, then include the code samples into the articles. The very early code snippets worked this way, but then we started just putting code inline. We've discussed this separation for making code examples more testable as well.
When this issue was created, we didn't have the overall Terraform code testing conversation. I agree that rather than adding the formatting separately, the testing repo and associated GH action can take care of code formatting as well. Closing this issue as this work will be part of the broader Terraform code testing effort.
What's wrong?
Currently, formatting embedded Terraform code within RST files is a manual process. The proposal is to run a GitHub Actions job in the CI workflow that will automatically format any embedded Terraform code within RST files. Rather than having this job run with every PR, the job should run only if there’s any code change under https://github.com/aiven/devportal/tree/main/docs/tools/terraform
Any other information
The RST support has been added to terrafmt via katbyte/terrafmt#60
The text was updated successfully, but these errors were encountered: