Skip to content
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

[rebase] Add Azure provider #899

Merged
merged 1 commit into from
Jan 30, 2015
Merged

[rebase] Add Azure provider #899

merged 1 commit into from
Jan 30, 2015

Conversation

phinze
Copy link
Contributor

@phinze phinze commented Jan 30, 2015

Rebased from #770 - verified acceptance tests pass locally. Should pass Travis as well.

Thanks @frodenas!!

@phinze
Copy link
Contributor Author

phinze commented Jan 30, 2015

Should pass Travis as well.

HUBRIS! 😀

Investigating...

phinze added a commit that referenced this pull request Jan 30, 2015
Currently when running `make updatedeps` from a branch, the dependency
list from master ends up getting used. We tried to work around this in
35490f7, and got part way there, but
here's what was happening:

 - record the current SHA
 - run `go get -f -u -v ./...` which ends up checking out master
 - master is checked out early in the `go get` process, which means all
   subsequent dependencies are resolved from master
 - re-checkout the recorded SHA
 - run tests

This works in most cases, except when the branch being tested actually
changes the list of dependencies in some way.

Here we move away from letting `go get -v` walk through everything in
`./...`, instead building our own list of dependencies with the help of
`deplist`. We can then filter terraform packages out from the list, so
they don't get touched, and safely update the rest.

This should solve problems like those observed in #899 and #900.

__Note__: had to add a feature to deplist to make this work properly;
see phinze/deplist@016ef97
Working on getting it accepted upstream.
@phinze phinze force-pushed the 770-azure-provider branch from 9894f50 to f561e2a Compare January 30, 2015 22:32
@phinze
Copy link
Contributor Author

phinze commented Jan 30, 2015

Well that was a fun little jaunt into go/build ... time to land this sucker ✈️

phinze added a commit that referenced this pull request Jan 30, 2015
@phinze phinze merged commit 8749d00 into master Jan 30, 2015
@phinze phinze deleted the 770-azure-provider branch January 30, 2015 22:36
@phinze phinze mentioned this pull request Jan 30, 2015
yahyapo pushed a commit to yahyapo/terraform that referenced this pull request Mar 13, 2015
Currently when running `make updatedeps` from a branch, the dependency
list from master ends up getting used. We tried to work around this in
35490f7, and got part way there, but
here's what was happening:

 - record the current SHA
 - run `go get -f -u -v ./...` which ends up checking out master
 - master is checked out early in the `go get` process, which means all
   subsequent dependencies are resolved from master
 - re-checkout the recorded SHA
 - run tests

This works in most cases, except when the branch being tested actually
changes the list of dependencies in some way.

Here we move away from letting `go get -v` walk through everything in
`./...`, instead building our own list of dependencies with the help of
`deplist`. We can then filter terraform packages out from the list, so
they don't get touched, and safely update the rest.

This should solve problems like those observed in hashicorp#899 and hashicorp#900.

__Note__: had to add a feature to deplist to make this work properly;
see phinze/deplist@016ef97
Working on getting it accepted upstream.
@ghost
Copy link

ghost commented May 4, 2020

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.

@ghost ghost locked and limited conversation to collaborators May 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants