Why the source_credentials_secret is showing in the deliverable instead of gitops_credentials_secret

Products

• VMware Tanzu Platform - Kubernetes

Issue/Introduction

When you add --param gitops_credentials_secret=git-basic and --param source_credentials_secret=git-basic during creating the workload, you will find the output of deliverable which is showing like the below:

apiVersion: carto.run/v1alpha1
kind: Deliverable
metadata:
  name: app_name
  labels:
    app.kubernetes.io/part-of: app_name
    apps.tanzu.vmware.com/has-tests: "true"
    apps.tanzu.vmware.com/workload-type: web
    app.kubernetes.io/component: deliverable
    app.tanzu.vmware.com/deliverable-type: web
    carto.run/cluster-template-name: external-deliverable-template
    carto.run/resource-name: deliverable
    carto.run/supply-chain-name: source-test-to-url
    carto.run/template-kind: ClusterTemplate
    carto.run/template-lifecycle: mutable
    carto.run/workload-name: app_name
    carto.run/workload-namespace: demo
spec:
  params:
  - name: source_credentials_secret
    value: git-basic
  source:
    git:
      url: https://gitops_server_address/dscpdevops/repository_name/_git/repository_name
      ref:
        branch: main

The source_credentials_secret is only showing in the deliverable output.

Resolution

When the workload creates the deliverable, the workload's gitops_credentials_secret param will be written into the deliverable's source_credentials_secret.

Because from the standpoint of the deliverable, the gitops repository is the only "source".