Skip to content
This repository has been archived by the owner on Jul 3, 2023. It is now read-only.

[question] Stack version locking #102

Open
micahlmartin opened this issue Mar 7, 2017 · 1 comment
Open

[question] Stack version locking #102

micahlmartin opened this issue Mar 7, 2017 · 1 comment

Comments

@micahlmartin
Copy link

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:

module "stack" {
  source             = "github.com/segmentio/stack"
}

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:

module "stack" {
  source             = "github.com/segmentio/stack?ref=1.0.0"
}

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.

@LegNeato
Copy link

Not using it yet, but couldn't you just fork it and point to your fork? Then you would be in control of updating as you see fit.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants