Ying Li bdfbd22afb Redact the swarm's spec's signing CA cert when getting swarm info, because ... otherwise if the user gets the info from the API, makes a non-CA related change, then updates, swarm will interpret this as the user trying to remove the signing key from the swarm. We are redacting due to usability reasons, not because the signing cert is secret. The signing KEY is secret, hence it's redacted. Signed-off-by: Ying Li <ying.li@docker.com>		2017-06-15 18:26:01 -07:00
..
config.go	Add config APIs	2017-05-11 10:08:21 -07:00
container.go	Add config APIs	2017-05-11 10:08:21 -07:00
network.go	Vendor swarmkit 7e096ced	2017-05-23 15:01:35 -07:00
node.go	Propagate the swarm cluster and node TLS info provided by the swarm	2017-05-10 11:29:17 -07:00
secret.go	Fixing #24631, inspect output on swarm object types without labels is empty object {}	2017-02-15 01:25:55 -05:00
service.go	remove RuntimeData from cluster and types	2017-05-19 17:10:32 -04:00
service_test.go	add service convert tests	2017-04-11 14:02:02 -04:00
swarm.go	Redact the swarm's spec's signing CA cert when getting swarm info, because	2017-06-15 18:26:01 -07:00
task.go	Fix dropped field in task translation from GRPC to REST	2017-03-07 14:55:15 -08:00