-
Notifications
You must be signed in to change notification settings - Fork 3
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
Advocate tags that comply with the standard #30
Comments
@explorigin Shall the version be a 7-digit hash of the git commit as per the RSS tagging standard? |
Actually, I don't recommend it at all. If we have the commit hash as a tag on every asset we either have to ignore that tag in the lifecycle settings or update that resource on every apply. (-: (ask me how I know!) |
Removed |
For our use case, we'll most likely end up running terraform commands only once when setting up the infrastructure (S3 buckets) for the new micro-ui, so it doesn't hurt to keep the version. Ooc :), does the
|
The example I saw was more like: lifecycle {
ignore_changes = [
tags["version"]
]
} But I didn't try it so I'm not certain that it will work. |
The default tags specified in https://github.com/RSS-Engineering/terraform/blob/main/backend_state_init/backend.tf.sample#L17 should be changed to meet two standards:
For RPCS:
confidentiality
to "Confidential" - this is a base default and can be modified but we want it to be secure by defaultFor RSS:
env
(doubles withenvironment
but better to have both)service
- name of the appThe text was updated successfully, but these errors were encountered: