-
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
Support insecure flag on artifact #20126
Conversation
8288da6
to
affbb8a
Compare
affbb8a
to
0f549ff
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking great, @amirabbas8! Just the one change around CI testing and I think we should be good.
Oh you'll also want to run |
0f549ff
to
79dd8b3
Compare
@shoenig, Thanks for your review. I have made the changes 🤩 |
Hey @amirabbas8 this is very close! Looks like there's a couple failing tests that need to be tweaked. I'm pretty sure in both cases it's just a matter of the test case comparing struct equality and not taking into account the new field. You can ignore the Vercel failures, that's some frontend stuff.
and
|
79dd8b3
to
3aac211
Compare
@shoenig, I fixed both test cases, thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM; thanks @amirabbas8!
Hey, I'm so glad this is my first PR to nomad. 🎉
this PR supports an insecure flag for artifact download as described in #19883
The artifact block now supports an insecure flag like the example below. this flag will prevent the go-getter from validating the TLS certificate.
Closes #19883