-
Notifications
You must be signed in to change notification settings - Fork 18.6k
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
Remove swarm inspect and use info instead #24492
Conversation
fmt.Fprintf(dockerCli.Out(), " Acceptance Policies:\n") | ||
for _, policy := range info.Swarm.Cluster.Spec.AcceptancePolicy.Policies { | ||
fmt.Fprintf(dockerCli.Out(), " %s:\n", policy.Role) | ||
fmt.Fprintf(dockerCli.Out(), " auto-accept: %t\n", policy.Autoaccept) |
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.
I feel Auto-acceptance
and Secret
are better for consistency
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.
@AkihiroSuda you're right 👍
61f43f5
to
978d220
Compare
A few remarks about acceptance policies:
|
978d220
to
9fe76d1
Compare
Rebased and hopefully, tests fixed 👼
That's an idea, I'll look into it. |
9fe76d1
to
6b47a0c
Compare
Hum, removing I'm not sure we should remove it, just adding Cluster information in @thaJeztah @icecrime wdyt ? |
Perhaps we can keep the |
@vdemeester sorry but would you mind linking where |
I think it's ok for |
Also 😉
|
@icecrime ok, I'll update and prepare a PR for engine-api. The test failure is related to that 😉 |
6b47a0c
to
a344dd6
Compare
Updated, fixed test failures and created a PR in |
@vdemeester let's keep the API unchanged and have |
@tiborvass you mean |
a344dd6
to
92c7aa5
Compare
92c7aa5
to
ec2f656
Compare
Updated 👼 |
@vdemeester |
@vieux ah damn.. revert the wrong file… I'll fix 👼 |
56e8729
to
8eb3f97
Compare
@vdemeester some updates we need on this one:
|
Can we add an Another question. Will |
Ok this mean I need to make a PR in engine-api 👼
Removing only in |
Hey Ken, regarding IsLeader, I think you can grab that from docker node I do agree it'd be useful in docker info regardless so +1 for that request On Saturday, July 23, 2016, Vincent Demeester notifications@github.com
|
@aluzzardi thanks for the work around. The one issue with |
Indeed - but for your use case, you can assume that if it's not a manager However I do still agree with you that this information should be available On Saturday, July 23, 2016, Ken Cochrane notifications@github.com wrote:
|
8eb3f97
to
9a134db
Compare
Remove the swarm inspect command and use docker info instead to display swarm information if the current node is a manager. Signed-off-by: Vincent Demeester <vincent@sbr.pm>
9a134db
to
3cf0b15
Compare
@vdemeester I was thinking about not returning join tokens via the /info API at all not just CLI |
Carried in #25042 |
Remove the
docker swarm inspect
command and usedocker info
instead to display swarm information if the current node is a manager 🐮.This only change the cli side and the return of
/info
but not the/swarm/inspect
endpoint. The attribute used in the info endpoint isSwarm.Cluster
and is populated only when the node is a manager.I did not add all the thing displayed by
swarm inspect
but they are available through the API.Remove/swarm/inspect
endpoint ?I'll create a
engine-api
if this pass design-review 😉Closes #24148
/cc @aluzzardi @tiborvass @stevvooe @tonistiigi
Signed-off-by: Vincent Demeester vincent@sbr.pm