[DOCUMENTATION] Why name field of secret is not documented?

[YuryHrytsuk]

Problem

I would expect to see the examples of using name field for docker secrets below:

• https://docs.docker.com/reference/compose-file/secrets/
• https://docs.docker.com/compose/how-tos/use-secrets/

Related PRs

• Add "name" field to secrets and configs to allow interpolation in Compose files cli#668

Why does it matter

I am currently trying to workaround the "immutability" of docker configs / secrets by using version-pinned name. Read more below:

• https://blog.sunekeller.dk/2019/01/docker-stack-deploy-update-configs/
• https://blog.viktoradam.net/2018/02/28/swarm-secrets-made-easy/

[ndeloof]

This is well documented in the compose-spec : https://github.com/compose-spec/compose-spec/blob/main/09-secrets.md
I'm not sure why docs isn't aligned with this reference. cc @aevesdocker

[YuryHrytsuk]

This is well documented in the compose-spec : https://github.com/compose-spec/compose-spec/blob/main/09-secrets.md I'm not sure why docs isn't aligned with this reference. cc @aevesdocker

@ndeloof as far as I understand, the change of name attribute will trigger automatic update of service relying on it. This can be used to update secrets (also configs) on running services which otherwise does not work "out of the box" (e.g. on docker stack deploy) (the official documentation on how to update docker configs with some manual actions)

Do you think it is worth documenting this behavior?

Please, read more about this below:

• https://blog.sunekeller.dk/2019/01/docker-stack-deploy-update-configs/
• https://blog.viktoradam.net/2018/02/28/swarm-secrets-made-easy/

[ndeloof]

unfortunately change to name attribute will not update containers using docker compose
I can't tell about docker swarm, as this repo is about compose, and swarm is 100% a different codebase