Docker.github.io: To doc: Add support for templated secrets and configs

[gbarr01]

References:
https://github.com/docker/docker-ce/blob/v18.03.0-ce-rc3/CHANGELOG.md
https://github.com/docker/cli/pull/896
https://github.com/moby/moby/pull/33702
https://github.com/moby/moby/pull/36366
https://github.com/docker/swarmkit/pull/2133

Possible doc locations:
https://docs.docker.com/engine/swarm/secrets/

[thaJeztah]

Wrote down a basic example here; https://github.com/moby/moby/issues/37377#issuecomment-401870956

[thaJeztah]

@ahh-docker PTAL

[ghost]

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!

[jean-airoldie]

This blog offers decent documentation in the meantime.

[matthanley]

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!

Does that mean usage of this feature will be changing? Any details of the referenced _refactor_?

[ev3rl0ng]

Hi, long time listener, first time caller. Sorry to revive an old thread, but I am trying to find more details around this very topic.

I was hoping to find out what the expected scope of the template would be in the case of a service or a stack deployment.

For example, could I:

• reference all replicas in a service with an array in a range style template from the golang Templates library?
• reference properties of another service in the same stack?

I understand that other platforms (terraform/ansible/puppet) could most likely provide what I'm looking for here, but there's a unique position that the config level templating provides here that those platforms would end up using or accomplishing via other means.

If I can get some initial pointers on where to start (new to this code base), I'd be more than happy to dig into it and generate the documentation around it if it is indeed possible.

Thanks for your time!