get -update doesn't update from non-master branches

[clstokes]

I'm using git remote modules (hosted in a private repo on GitHub) and specifying a branch other than master. However, it seems when using a branch other than master, modules are not updated when I run get -update. If modules are pulled from master, then they're updated fine.

Using v0.4.2...

Steps to reproduce

1. Create module module1 in repo repo-modules.
2. Create project project1 in repo repo-main, that uses module1.
3. In project1, run get and plan to see changes you expect.
4. Create changes to module1 on branch branch1.
5. Update your source URL to use branch1 with ?ref=branch1.
6. In project1, run get -update and plan. Your should not see the changes you expect.

If it matters the source URL I'm using is in the form git::ssh://[email protected]/org/repo-modules.git//module1?ref=branch1.

Updated with Terraform version.

[radeksimko]

I don't see this being problem in case of git tags used as versions as these will not likely ever be updated. In fact, you can't actually update a tag in any clean way, it's just a pointer to git hash which won't be pointing anywhere else unless you push --force such change (correct me if I'm wrong).

In case of real branches, it is an issue though.

[rradecki]

+1
We want also to use branches other than master and I think that this functionality should be implemented. When is it going to be done?

[ghost]

+1

[pmilewsk]

+1

[amaczuga]

please do fix this

[sszwed]

+1

[rradecki]

Is there any ETA for this issue?

[elblivion]

+1

[bennycornelissen]

+1

[djvdorp]

+1 for this, the issue still exists in v0.6.6 when trying to use ?ref=branch1.

Workaround for an upgrade-like experience (clean and re-clone)

rm -rf .terraform/modules/
terraform get
terraform plan

[mitchellh]

Working on this now

[mitchellh]

Fix is in PR, will be fixed in the next release of TF

[djvdorp]

@mitchellh great, thanks for your work, very much appreciated! When is the next release of TF scheduled?

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.