Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct multiple secret values in one array parameter that references different secret variables #1566

Conversation

SaschaSchwarze0
Copy link
Member

Changes

There is a bug when defining the following Build:

spec:
  paramValues:
    name: param-name
    values:
    - secretValue:
        name: secret-name
        key: key-1
        format: ARG_NAME1=${SECRET_VALUE}
    - secretValue:
        name: secret-name
        key: key-2
        format: ARG_NAME2=${SECRET_VALUE}

Due to the way we iterate over the values, we caused the TaskRun to only have references to key-2. Unfortunatly, our existing unit test did not capture that. Also extending those.

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

Release Notes

The usage of different secrets or secret keys as values inside one array parameter is now possible

@SaschaSchwarze0 SaschaSchwarze0 added the kind/bug Categorizes issue or PR as related to a bug. label Apr 2, 2024
@SaschaSchwarze0 SaschaSchwarze0 added this to the release-v0.14.0 milestone Apr 2, 2024
@pull-request-size pull-request-size bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Apr 2, 2024
@openshift-ci openshift-ci bot added the release-note Label for when a PR has specified a release note label Apr 2, 2024
@openshift-ci openshift-ci bot requested review from otaviof and qu1queee April 2, 2024 10:13
Copy link
Contributor

@qu1queee qu1queee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 2, 2024
Copy link
Contributor

openshift-ci bot commented Apr 2, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qu1queee

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 2, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 5300509 into shipwright-io:main Apr 2, 2024
12 checks passed
@SaschaSchwarze0 SaschaSchwarze0 deleted the sascha-fix-multiple-params branch May 5, 2024 16:09
@SaschaSchwarze0
Copy link
Member Author

/cherrypick release-v0.13

@openshift-cherrypick-robot

@SaschaSchwarze0: new pull request created: #1593

In response to this:

/cherrypick release-v0.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release-note Label for when a PR has specified a release note size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

3 participants