Skip to content

fix(style-guide): Adjust rule four for var validation to exclude bool… #21

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.

Sign up for GitHub

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

Merged
RemoteRabbit merged 1 commit into from
May 14, 2026
Merged

fix(style-guide): Adjust rule four for var validation to exclude bool… #21

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/terraform/style-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,8 @@ lowercase with only letters and underscores.
for multiline detailed descriptions.
3. Be explicit when it comes to variable types. If it is a map or object be diligent with marking that in the type along
with its internal types.
4. All variables should have at least one level of validation. Even if it is a simple variable that is always set in a
vars file. Typos and mistakes happen. Validation catches that ahead of time.
4. All variables should have at least one level of validation, excluding variables of type `bool`. Even if it is a
simple variable that is always set in a vars file. Typos and mistakes happen. Validation catches that ahead of time.
5. Create a condition that is as strict to the type and desired state of the variable without it becoming its own
project to manage. Strict enough to catch real mistakes, loose enough not to require updating every time the
upstream naming rules shift.
Expand Down
Loading