Expose Docker Image labels as Project Variables

[zentron]

Unlike standard "package" deployments, were we can extract, access and transform configuration files contained within them, docker images are presented as much more of a black-box artefact.

One approach that can be leveraged however is the label metadata that can be applied to images at build time. With this mechanism a user can embed some configuration or values required by octopus at deployment time, which will then be added to the docker project variable dictionary indexed via the image packageId.
so If we add a label at build time with

LABEL com.acme.foo="bar"

And we use this image named as Acme in a script step, then at deploy time a variable will be available at the location
Octopus.Action.Package[Acme].Image.Labels[ com.acme.foo] with the value bar. Since this value is added to the variable dictionary, it means that the value itself can make use of the standard Octopus variable substitution syntax.

The labels com.octopus.* and Octopus.* should be avoided and are reserved for future Octopus functionality.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.