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

Backport of Upgrade go-getter to v1.5.0 into v0.14 #26806

Merged

Conversation

teamterraform
Copy link
Contributor

Backport

This PR is auto-generated from #26762 to be assessed for backporting due to the inclusion of the label 0.14-backport.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

The below text is copied from the body of the original PR.


Upstream changelog:

v1.5.0

v1.4.2

  • Expose a Umask option to mask file permissions when storing local files or decompressing an archive. Helpful for clearing setuid or other sensitive bits.
  • feat(detector): provide a detector for repositories hosted on GitLab.com
  • Use default AWS credential chain under normal circumstances

Also run go mod tidy.

Fixes #20439 (via the AWS credential chain change in 1.4.2)

@hashicorp-cla
Copy link

hashicorp-cla commented Nov 4, 2020

CLA assistant check
All committers have signed the CLA.

Includes fix for breaking upstream API change.
@alisdair alisdair force-pushed the backport/alisdair/upgrade-go-getter/formerly-pleasant-rhino branch from 45d5c85 to 0cd6261 Compare November 4, 2020 14:16
@codecov
Copy link

codecov bot commented Nov 4, 2020

Codecov Report

Merging #26806 into v0.14 will increase coverage by 0.00%.
The diff coverage is 100.00%.

Impacted Files Coverage Δ
internal/providercache/package_install.go 17.77% <100.00%> (ø)
terraform/evaluate.go 53.11% <0.00%> (+0.41%) ⬆️

@alisdair alisdair merged commit f02e97c into v0.14 Nov 4, 2020
@alisdair alisdair deleted the backport/alisdair/upgrade-go-getter/formerly-pleasant-rhino branch November 4, 2020 14:21
@ghost
Copy link

ghost commented Dec 5, 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 as resolved and limited conversation to collaborators Dec 5, 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.

None yet

3 participants