Uploaded image for project: 'Hybrid Cloud Console'
  1. Hybrid Cloud Console
  2. RHCLOUD-25035

Bonfire does not respect overriding IMAGE_TAG when dependencies are involved

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Unset
    • No
    • Platform Pipeline Sprint 62, Platform Pipeline Sprint 63, Platform Pipeline Sprint 64, Platform Pipeline Sprint 65, Platform Pipeline Sprint 66, Platform Pipeline Sprint 67, Platform Pipeline Sprint 68, Platform Pipeline Sprint 69, Platform Pipeline Sprint 70, Platform Pipeline Sprint 71, Platform Pipeline Sprint 72, Platform Pipeline Sprint 73
    • Normal

      This was noticed as an issue by rhn-support-dehort which I decided to investigate. After having a great call with vmugicag brainstorming this, we figured out it was due to dependency resolution.

      Issue: IMAGE_TAG not respected with a config.yaml, but is respected via a cli-flag

      Reproduction

      Run bonfire deploy ingress-local with a config.yaml that looks like this

      appsFile:
        host: gitlab
        repo: insights-platform/cicd-common
        path: bonfire_configs/ephemeral_apps.yaml
      apps:
        - name: ingress-local
          components:
            - name: ingress-local
              host: local
              repo: "/some/path/to/repo/insights-ingress-go"
              path: /deploy/clowdapp.yaml
              parameters:
                IMAGE_TAG: pr-319-latest

      Workaround: Specify all the dependencies before your app. For example with ingress: bonfire deploy host-inventory payload-tracker ingress-local (using that yaml above again) or bonfire deploy ingress --set-image-tag quay.io/cloudservices/insights-ingress=pr-319-latest
       

            bschneid@redhat.com Brandon Schneider
            bschneid@redhat.com Brandon Schneider
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: