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 Jul 3, 2023. It is now read-only.
Are there any plans to version the stack to lock in the functionality? Currently when creating an instance of the stack the default behavior is to pull the latest from master:
Unless you always 100% guarantee everything is backwards compatible this creates problems when you have long-running instances and automation. If I don't check-in the .terraform/modules folder into my repo anytime I do terraform get I'm going to get updated modules.
Terraform has the ability to specify a branch/version with:
This would guaranteed we always got the version we currently had deployed and would not run into a situation where we suddenly got a diff that could cause issues.
I'm curious to hear as to how other people are solving this.
The text was updated successfully, but these errors were encountered:
Are there any plans to version the stack to lock in the functionality? Currently when creating an instance of the stack the default behavior is to pull the latest from master:
Unless you always 100% guarantee everything is backwards compatible this creates problems when you have long-running instances and automation. If I don't check-in the
.terraform/modules
folder into my repo anytime I doterraform get
I'm going to get updated modules.Terraform has the ability to specify a branch/version with:
This would guaranteed we always got the version we currently had deployed and would not run into a situation where we suddenly got a diff that could cause issues.
I'm curious to hear as to how other people are solving this.
The text was updated successfully, but these errors were encountered: