akuity / kargo

Application lifecycle orchestration
https://kargo.akuity.io/
Apache License 2.0
1.56k stars 137 forks source link

bug(ui) Support of Multi-Pipeline Freights with promotionTemplate steps not working #2734

Open dan1el-k opened 2 hours ago

dan1el-k commented 2 hours ago

Checklist

Description

The previously improved Multi-Pipeline support in the UI seems to not working.

I used 2 git subscriptions per Warehouse.

The UI however just show the latest Freight. The "next" buttons are missing, which were introduced in #2353

apiVersion: kargo.akuity.io/v1alpha1
kind: Stage
metadata:
  annotations:
    argocd.argoproj.io/sync-options: SkipDryRunOnMissingResource=true
  name: kube2-dev-common
  namespace: mercury-debug
  finalizers:
    - kargo.akuity.io/finalizer
spec:
  promotionTemplate:
    spec:
      steps:
        - config:
            checkout:
              - branch: main
                path: ./mm
              - branch: stage/kube2-dev-common
                create: true
                path: ./out
            repoURL: 'https://my-domain/my-org/mercury-manifest.git'
          uses: git-clone
        - config:
            checkout:
              - fromFreight: true
                fromOrigin:
                  kind: Warehouse
                  name: mercury-dex
                path: ./dex
            repoURL: 'https://my-domain/my-org/mercury-dex-manifest.git'
          uses: git-clone
        - config:
            checkout:
              - fromFreight: true
                fromOrigin:
                  kind: Warehouse
                  name: mercury-apptio-agent
                path: ./apptio-agent
            repoURL: 'https://my-domain/my-org/mercury-apptio-agent-manifest.git'
          uses: git-clone
        - config:
            inPath: ./mm/applications
            outPath: ./out
          uses: copy
        - config:
            inPath: ./dex/deployment
            outPath: ./out/mercury-dex/stages/kube2-dev/deployment
          uses: copy
        - config:
            inPath: ./apptio-agent/deployment
            outPath: ./out/mercury-apptio-agent/stages/kube2-dev/deployment
          uses: copy
        - config:
            message: Always pass on what you have learned.
            path: ./out
          uses: git-commit
        - config:
            path: ./out
            targetBranch: stage/kube2-dev-common
          uses: git-push
  requestedFreight:
    - origin:
        kind: Warehouse
        name: mercury-dex
      sources:
        direct: true
    - origin:
        kind: Warehouse
        name: mercury-apptio-agent
      sources:
        direct: true

Screenshots

Project image

Freigts image

Steps to Reproduce

Version

0.9.0

Logs

Paste any relevant application logs here.
krancour commented 2 hours ago

@dan1el-k does stage.status.freightHistory[0] properly reflect both pieces of Freight, one from each origin?