Issue Type: | Bug |
---|---|
Priority: | 4 - Normal |
Status: | Resolved |
Created at: | 2020-01-27T12:06:57.298Z |
Updated at: | 2022-04-01T01:04:43.674Z |
Created by: | Former user |
---|---|
Reported by: | Former user |
Assigned to: | Former user |
Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2020-01-28T10:59:11.424Z)
2020-01-30 Kenny Rogers Roasters (Release Date: 2020-01-30)
During TRITON-2052, I came across a couple of fixes that standalone imgapi could do with:
I tested these changes in concern with TRITON-2052
Nit - can the title ticket be updated to "Allow imgapi standalone testing using a self signed certificate"?
I can do, but the changes cover a bit more than that?
To me it seems the bulk of the changes are around allowing self signed certificate - if you can find a way to incorporate that in the title I would feel better. Sometime later, when someone is using git log or the looking for jira tickets - the message "standalone imgapi could be easier to test with" won't be very helpful in my opinion (that could cover anything in standalone imgapi testing, heh).
sdc-imgapi commit f0352ad4d455322489cbac64a613bf96c5f3d1a2 (branch master, by John Levon)
TRITON-2053 imgapi could have better support for self-signed certs (#27)
Reviewed by: Trent Mick <trentm@gmail.com>
Reviewed by: Todd Whiteman <todd.whiteman@joyent.com>