swarm/init: Fix --external-ca ignoring cacert option#5995
swarm/init: Fix --external-ca ignoring cacert option#5995thaJeztah merged 2 commits intodocker:masterfrom
--external-ca ignoring cacert option#5995Conversation
|
Am I wrong here, or has this been broken for 7 years and nobody noticed? 🤣 |
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
f341ce3 to
a5aa4c5
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
a5aa4c5 to
e41ef5b
Compare
Oh, someone noticed,
(and there's a couple of, now archived, internal issues tracking it); ISTR there was a security-related issue attached at some point, and there was some discussion whether the feature had to be restored or removed, and that's where things got stuck. |
|
Actually this isn't the same issue - the PRs you mention deal with the first cert being empty instead of defaulting to the "Trusted CA Root". This PR is about the second cert which the CLI doesn't even pass to the swarm. |
31d6292 mistakenly changed the `ToSpec` function to set all certs passed via `external-ca` to empty strings. Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
e41ef5b to
6c2d023
Compare
thaJeztah
left a comment
There was a problem hiding this comment.
LGTM
lets bring this one in
- What I did
31d6292 mistakenly changed the
ToSpecfunction to set all certs passed viaexternal-cato empty strings.- How I did it
- How to verify it
integration-cliBefore:
After
$ go test -run TestSwarmInitWithExternalCA PASS ok github.com/docker/cli/cli/command/swarm 1.009- Human readable description for the release notes
- A picture of a cute animal (not mandatory but encouraged)