-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Improve documentation about artifact downloading #1219
Comments
Closing with #1232 |
Thank you! |
@pshima Let's not close it yet, we might be able to do some validation here in the cli. |
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. 😄 |
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. |
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.The text was updated successfully, but these errors were encountered: