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

Fix the value for APISecretNamespaceKey #5492

Merged
merged 1 commit into from
Sep 14, 2022

Conversation

chuangw6
Copy link
Member

Changes

Related to #5450.

The key for APISecretNamespace in the configmap is named api-token-secret-namespace, but the value of APISecretNamespaceKey in pkg/resolution/resolver/git/config.go is api-token-namespace. This will cause resolver to fail to get API token.

In this PR, we use the correct key name api-token-secret-namespace.

Signed-off-by: Chuang Wang chuangw@google.com

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs included if any changes are user facing
  • Has Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

Related to tektoncd#5450.

The key for APISecretNamespace in the configmap is named `api-token-secret-namespace`,
but the value of `APISecretNamespaceKey` in `pkg/resolution/resolver/git/config.go`
is `api-token-namespace`. This will cause resolver to fail to get API token.

In this PR, we use the correct key name `api-token-secret-namespace`.

Signed-off-by: Chuang Wang <chuangw@google.com>
@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Sep 13, 2022
@chuangw6
Copy link
Member Author

/kind bug

@tekton-robot tekton-robot added the kind/bug Categorizes issue or PR as related to a bug. label Sep 13, 2022
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 13, 2022
@chuangw6
Copy link
Member Author

@abayer Please take a look. Thanks

@abayer
Copy link
Contributor

abayer commented Sep 13, 2022

/approve

Good catch - thanks!

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abayer

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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 13, 2022
@abayer
Copy link
Contributor

abayer commented Sep 14, 2022

/lgtm

I want to make sure this gets into v0.40, so I'm cheating. =)

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 14, 2022
@tekton-robot tekton-robot merged commit b7c29b4 into tektoncd:main Sep 14, 2022
@chuangw6
Copy link
Member Author

/lgtm

I want to make sure this gets into v0.40, so I'm cheating. =)

SG! Thanks @abayer

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-none Denotes a PR that doesnt merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants