Closed brikis98 closed 4 years ago
In https://github.com/hashicorp/terraform-aws-consul/pull/192, I updated the build to use a different Docker image, with a newer version of Go that doesn't rely on everything running in the /go/xxx path. Unfortunately, I forgot to update the deploy portion of the build, which publishes AMIs, and was still relying on those paths. This PR fixes the deploy step. I created a temporary, internal release to validate it, as the deploy step doesn't run on branches, by default: https://github.com/hashicorp/terraform-aws-consul/releases/tag/v0.8.1-internal-test
/go/xxx
Gah, WTH... Why does my PR get merged when I do an internal release of it???
In https://github.com/hashicorp/terraform-aws-consul/pull/192, I updated the build to use a different Docker image, with a newer version of Go that doesn't rely on everything running in the
/go/xxx
path. Unfortunately, I forgot to update the deploy portion of the build, which publishes AMIs, and was still relying on those paths. This PR fixes the deploy step. I created a temporary, internal release to validate it, as the deploy step doesn't run on branches, by default: https://github.com/hashicorp/terraform-aws-consul/releases/tag/v0.8.1-internal-test