0a64d51c3d
After recent conversations, we've come to the conclusion it will be good to have two models of promotion - using tags, where gate directly uploads to the final repository and promote retags the image. - from an intermediate-registry, where upload stores the built image in an i-r and the promote step uploads to the final registry. To facilitate this, we add a "promote_container_image_method" flag to the promote roles. The documentation is expanded to explain how all this is intended to work together. These roles haven't been publicised yet, but this should be a no-op as it defaults to tags, which is the current operation. c.f. Ia24bbd101e01ab371ceacfed006b5ff806418a97 Change-Id: I1c25f60f835b1cab983bcdd169eeffc0e250a56c
9 lines
363 B
YAML
9 lines
363 B
YAML
- name: Promote container image with tags
|
|
when: promote_container_image_method|default('tag') == 'tag'
|
|
include_tasks: promote-from-tag.yaml
|
|
|
|
- name: Promote container image with intermediate registry
|
|
when: promote_container_image_method|default('tag') == 'intermediate-registry'
|
|
fail:
|
|
msg: 'The intermediate-registry promote role is not yet complete'
|