-
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
deps: investigate steps needed for updating go-getter #16541
Comments
|
Just FYI hashicorp/terraform#28968 is blocked on having a new release cut for go-getter (v1), which my understanding is the Nomad team will create when you have resolved the questions in this issue. Linking these issues so I can more easily check in on status. :) |
Hi @shoenig, @picatz: according to @kmoe, the Nomad team agreed to make a new release of |
Hi @crw! Sorry, I think there was a miscommunication and we're fine with the change. We just need to figure out whether or not to special case the Landlock config in Nomad for it, but that's not something we need to block on at all. I've had a quick look at the go-getter repo and how the releases work and I think I've got a handle on that. I've just pushed the 1.7.2 tag and waiting for the release action to complete. |
@tgross thank you so much for your very prompt response! I appreciate it. |
go-getter release done: https://github.com/hashicorp/go-getter/releases/tag/v1.7.2 |
This has been long-since updated. Closing it out. |
If/When hashicorp/go-getter#300 is merged, we need to be careful in understanding the implications on Nomad's use of
go-getter
for artifact downloading. In particularIf
git
is now going to lookup the user's.gitconfig
, is it going to error when landlock blocks that access?Regardless of 1, now that
go-getter
would be able to access the user.gitconfig
, should we go ahead and allow that to happen?The text was updated successfully, but these errors were encountered: