Thanks Angie. I'll put this on the agenda for our upcoming doc team meeting. We'll assess impact to existing and future docs. Thx. -- Mike From: Wang, Jing (Angie) <Angie.Wang@windriver.com> Sent: Friday, October 4, 2019 10:48 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [docs]Changing Ansible docker_registries's "unified" key Hi All, I am changing the Ansible docker_registries's "unified" key to "defaults". From docker_registries: unified: url: to docker_registries: defaults: url: And the semantics for "defaults" is a bit different as before. The "defaults" now defines common values that to be applied to all override-able public registries but the values under the specific registries, if specified, will take precedence over the values under defaults registry. If you only use defaults key, it will apply url, username and password for all registries (docker.io, quay.io, gcr.io, k8s.gcr.io, docker.elastic.co) e.g. docker_registries: defaults: url: unified.io username: adminUser password: adminPass If you have something special for some particular registry/registries, you can override the values by specifying them under its own entry. e.g. docker_registries: docker.io: username: dockerUser password: dockerPass k8s.gcr.io: username: k8sUser password: k8sPass defaults: url: unified.io username: adminUser password: adminPass This affects anyone with a setup that specifies alternate docker registries that using "unified" key as they will need to change their Ansible localhost.yml files to use "defaults" after this commit. The change is currently under review: https://review.opendev.org/#/c/686057/ Thanks, -Angie