Make image registry regions configurable

Regions are already configurable in the publish task, although
one of the steps ignored the config, which is fixed in this PR.

Expose the imageRegistryRegions parameter in the pipeline too,
so that it may be controlled via the pipeline run.

Signed-off-by: Andrea Frittoli <[email protected]>

tekton/publish.yaml

@@ -197,8 +197,6 @@ spec:
       mkdir -p ${DOCKER_CONFIG}
       cp /workspace/docker-config.json ${DOCKER_CONFIG}/config.json
 
-      REGIONS="us eu asia"
-
       # Tag the images and put them in all the regions
       for IMAGE in $(cat /workspace/built_images)
       do

tekton/release-pipeline.yaml

@@ -16,6 +16,9 @@ spec:
   - name: imageRegistryPath
     description: The path (project) in the image registry
     default: tekton-releases
+  - name: imageRegistryRegions
+    description: The target image registry regions
+    default: "us eu asia"
   - name: versionTag
     description: The X.Y.Z version that the artifacts should be tagged with
   - name: releaseBucket
@@ -154,6 +157,8 @@ spec:
           value: $(params.imageRegistry)
         - name: imageRegistryPath
           value: $(params.imageRegistryPath)
+        - name: imageRegistryRegions
+          value: $(params.imageRegistryRegions)
         - name: releaseAsLatest
           value: $(params.releaseAsLatest)
         - name: serviceAccountPath