-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Upgrade go-getter #5445
Comments
The new version of go-getter now also supports GCS as a storage backend (see hashicorp/go-getter#170) and contains a number of fixes, e.g. for SCP style URLs when using the git provider (see hashicorp/go-getter#180). I'd be happy to help here if needed - what's needed to help push this over the line? |
There's an outstanding PR for updating go-getter: #5446 |
The status on this is "on hold". I haven't had the bandwidth to do the work stated in the comments. Summary of what's needed as follows:
|
Ah, that does seem like a bit more effort than I thought! I'd like to help where I can but it will take some learning to familiarize myself with the Nomad build and tests. It will be easier for me to help change go-getter which #5446 suggests is required. @prologic |
Yes! See this comment and this one |
Any progress with this? |
It seems that just updating go-getter isn't enough
should have 'gcs' in the supported list - supported = []string{"http", "https", "s3", "hg", "git"}
+ supported = []string{"http", "https", "s3", "hg", "git", "gcs"} |
go-getter has been upgraded to support GCS as an artifact source, but still does not support symlinks in tarballs. I'm closing the rest of this issue as duplicate of #2292 |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Need to upgrade the version of go-getter used to include the fix in hashicorp/go-getter#171
Also somewhat related (because of dependency management) #5444
The text was updated successfully, but these errors were encountered: