🌱 Image build, use variables for repo push

To help out people building images in a fork, use github action variables to be able to configure the target registry and image names. Now on a fork, the destination of an image build can be set by using Action Variables: - IMAGE_BUILD_REGISTRY (default: "quay.io/konveyor") - IMAGE_BUILD_IMAGE_NAME (default: "tackle2-ui") and secrets: - QUAY_PUBLISH_ROBOT - QUAY_PUBLISH_TOKEN Signed-off-by: Scott J Dickerson <[email protected]>
sjd78 · Sep 12, 2024 · 1b4ae76 · 1b4ae76
1 parent bf587d3
commit 1b4ae76
Showing 1 changed file with 6 additions and 2 deletions.
diff --git a/.github/workflows/image-build.yaml b/.github/workflows/image-build.yaml
@@ -13,12 +13,16 @@ concurrency:
   group: build-${{ github.ref }}
   cancel-in-progress: true
 
+# env:
+#   target_registry: ${{ vars.IMAGE_BUILD_REGISTRY || 'quay.io/konveyor' }}
+#   target_image_name: ${{ vars.IMAGE_BUILD_IMAGE_NAME || 'tackle2-ui' }}
+
 jobs:
   image-build:
     uses: konveyor/release-tools/.github/workflows/build-push-images.yaml@main
     with:
-      registry: "quay.io/konveyor"
-      image_name: "tackle2-ui"
+      registry: ${{ vars.IMAGE_BUILD_REGISTRY || 'quay.io/konveyor' }}
+      image_name: ${{ vars.IMAGE_BUILD_IMAGE_NAME || 'tackle2-ui' }}
       containerfile: "./Dockerfile"
 
       # keep the architectures in sync with `ci-image-build.yml`