Details
-
Story
-
Resolution: Done
-
Major
-
None
-
3
-
False
-
None
-
False
-
Params and results are now populated in workspace bindings.
-
Pipelines Sprint 256, Pipelines Sprint 257
Description
Description
What problem/issue/behavior are you having trouble with? What do you expect to see?
We are testing in PAC, this bug may exist in upstream Tekton.
When trying to define Tekton Paramters for ConfigMap/Secret Names, the Param is not being expanded and filling in the underlying value.
Example Snippet:
workspaces:
- name: clone-workspace
volumeClaimTemplate:
spec:
accessModes: - ReadWriteMany
resources:
requests:
storage: 1Gi
storageClassName: px-repl2-file
- Workspace to hold google credentials. The name of the configMap needs to be
- changed per environment
- name: google-creds
configMap:
name: google-creds-$(params.ENVIRONMENT). ### <---- Gets Passed in without Variable being Expanded
- This workspace will inject secret to help the git-clone task to be able to
- checkout the private repositories
- name: basic-auth
secret:
secretName: "{{ git_auth_secret }}" ### <--- This works
- This workspace will inject secret for sonarqube analysis
- name: sonar-credentials
secret:
secretName: $(tasks.get-params.results.ENVIRONMENT) ### <---- Gets Passed in without Variable being Expanded
What is the business impact? Please also provide timeframe information.
N/A