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.

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

clarify wording that variables should be used for code that could be … #25

Closed
wants to merge 1 commit into from
Closed

clarify wording that variables should be used for code that could be … #25

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
2 changes: 1 addition & 1 deletion code-structure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ Please make sure that you understand key concepts - [resource module](key-concep
* Like procedural code, Terraform code should be written for people to read first, consistency will help when changes happen six months from now
* It is possible to move resources in Terraform state file but it may be harder to do if you have inconsistent structure and naming
* Keep resource modules as plain as possible
* Don't hardcode values which can be passed as variables or discovered using data sources
* Don't hardcode values which can be passed as variables or discovered using data sources when creating modules that will be used by others
* Use data sources and `terraform_remote_state` specifically as a glue between infrastructure modules within composition
* \(add links to other blog posts\)

Expand Down