Repository navigation
fix: match token secrets that keep the provider name in the token name (#1090) - #1091
Conversation
#1090) * fix: match token secrets that keep the provider name in the token name isSecretMatchesSearchCriteria read the OAuth provider name from the che.eclipse.org/scm-provider-name annotation only. Secrets stored before that annotation was introduced keep the provider name in che.eclipse.org/scm-personal-access-token-name, so a lookup by provider name stopped matching them. Fall back to the token name when the provider name annotation is absent or empty, the same way getScmProviderName already does. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fixup! fix: match token secrets that keep the provider name in the token name --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: vinokurig The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Docker image build succeeded: quay.io/eclipse/che-server:pr-1091 kubectl patch commandkubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/cheServer/deployment", "value": {containers: [{image: "quay.io/eclipse/che-server:pr-1091", name: che}]}}]" |
isSecretMatchesSearchCriteria read the OAuth provider name from the che.eclipse.org/scm-provider-name annotation only. Secrets stored before that annotation was introduced keep the provider name in che.eclipse.org/scm-personal-access-token-name, so a lookup by provider name stopped matching them. Fall back to the token name when the provider name annotation is absent or empty, the same way getScmProviderName already does.
What does this PR do?
Screenshot/screencast of this PR
What issues does this PR fix or reference?
How to test this PR?
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or referenceandHow to test this PRcompletedRelease Notes
Reviewers
Reviewers, please comment how you tested the PR when approving it.