HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
hashicorp
go-getter
Go2017–2023
hashicorp / go-getter

go-getter

Package for downloading things from a string URL using a variety of protocols.

3Distinct people
3Mentions
0Explicit recommenders
1.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Package for downloading things from a string URL using a variety of protocols.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year3 dated mentions

Observed mentions: 2017-03-10 23:31:54 UTC to 2023-04-28 14:05:27 UTC.

012017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC110

What Hacker News says

3 sources
We have work in progress to support go-getter [1] allowing use of files from many different sources. There is a WIP branch [2] building that into the Steampipe Plugin SDK, so it can be immediately enabled for all our file based plugins (CSV, Terraform, etc) [3]. Watch this space and hopefully you can help us test! 1 - https://github.com/hashicorp/go-getter 2 - https://github.com/turbot/steampipe-plugin-sdk/compare/main.... 3 - https://github.com/turbot/steampipe-plugin-terraform/tree/ad...
In Select * from cloud
Nomad dev here. Great post! Hopefully I can provide some insights: > 1. Templated job files. While parameterized jobs[0] are a step toward templated jobs, they unfortunately don't address your use case. We'll be adding `-var` options to `run` in 0.7 to allow templating normal jobs like you can template jobs. In the meantime I think what you're doing is pretty good and should integrate well into a CI/CD pipeline for automating deploys of new builds. You could consider a specialized templating tool instead of sed like m4, a jinja-based tool like j2cli, or even consul-template. A number of users also bypass `nomad run ...` and run jobs through our HTTP API instead.[1] While this takes more code, it's easiest to build into existing deployment tooling (CI/CD, chatops, chef, etc) and obviously allows easy manipulation. > 2. Better documentation
Read the rest
. Absolutely. We're acutely aware of the need for more comprehensive docs. Expect a "Guides" section to appear in the near future to cover common use patterns like yours! > 3. Explicit support for artifact versioning? Probably not going to happen as it would be little more than an opaque meta var to Nomad.[2] Although in the upcoming 0.5.5 release we do support Git and hg URLs for artifacts, so you could pull down code from a tag.[3] We do have other artifact features planned for the near future though (like caching so common artifacts shared between jobs aren't downloaded multiple times), so perhaps some sort of versioning will be added. Not sure what the exact semantics will be yet. [0] https://www.hashicorp.com/blog/replacing-queues-with-nomad-d... [1] https://www.nomadproject.io/docs/http/job.html#put-post [2] https://www.nomadproject.io/docs/job-specification/artifact.... [3] https://github.com/hashicorp/go-getter#git-git
In Nomad Task Versioning

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.