We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Migrated from GitLab: https://gitlab.com/meltano/handbook/-/issues/68
Originally created by @aaronsteers on 2022-03-02 21:58:21
First raised here: https://gitlab.com/meltano/squared/-/merge_requests/70#note_860678737
For terraform resources, let's create a set of code standards:
guidelines such as: Code matches terraform fmt auto-format output. What docs are expected - inline and in markdown docs - for definition of done? Should we have a top-of-file "docstring" for each .tf file? camel_case vs kebab-case for resource and variable names? I personally favor camel_case but anyway the project currently uses both. Disallow using our own aws account IDs in .tf files. (Replaced by data refs, relative refs, or input vars.) ...
guidelines such as:
terraform fmt
camel_case
kebab-case
The text was updated successfully, but these errors were encountered:
View 10 previous comments from the original issue on GitLab
Sorry, something went wrong.
kgpayne
edgarrmondragon
No branches or pull requests
Migrated from GitLab: https://gitlab.com/meltano/handbook/-/issues/68
Originally created by @aaronsteers on 2022-03-02 21:58:21
First raised here: https://gitlab.com/meltano/squared/-/merge_requests/70#note_860678737
For terraform resources, let's create a set of code standards:
The text was updated successfully, but these errors were encountered: