Improve documentation about artifact downloading

[c4milo]

For instance, one very subtle detail that almost always bites me is that
instead of specifying the source mybucket.s3.amazonaws.com/containers/vault.tar.gz I always do it with the protocol scheme like so: https://mybucket.s3.amazonaws.com/containers/vault.tar.gz and nomad fails downloading the artifact from S3 with 403.

[pshima]

Closing with #1232

[c4milo]

Thank you!

[diptanu]

@pshima Let's not close it yet, we might be able to do some validation here in the cli.

[sethvargo]

Hi there,

This is done and there are now a ton of examples in both the job file and online documentation. I think it makes sense to push this kind of validation into go-getter if we want to do that validation, but it's also a relatively small win given the massive amount we've invested in documentation. I'm going to close out this issue, but it'll remain searchable for the future humans. 😄

[github-actions]

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.
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.