Skip to content

fix(core): make CREDENTIALS_CODE mutually exclusive with other credential sources#7615

Merged
smilkuri merged 3 commits intomainfrom
feature-id
Jan 5, 2026
Merged

fix(core): make CREDENTIALS_CODE mutually exclusive with other credential sources#7615
smilkuri merged 3 commits intomainfrom
feature-id

Conversation

@smilkuri
Copy link
Copy Markdown
Contributor

@smilkuri smilkuri commented Jan 2, 2026

Issue

Internal JS-6433

Description

This fixes double credential attribution where provider credentials (e.g., fromEnv()) were incorrectly getting both their specific source attribution and CREDENTIALS_CODE.

Testing

yarn test:integration

Checklist

  • [n/a] If the PR is a feature, add integration tests (*.integ.spec.ts).
  • [n/a] If you wrote E2E tests, are they resilient to concurrent I/O?
  • [n/a] If adding new public functions, did you add the @public tag and enable doc generation on the package?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@smilkuri smilkuri requested a review from a team as a code owner January 2, 2026 16:59

// Only set CREDENTIALS_CODE if user provided a credential object
if (isCredentialObject) {
return setCredentialFeature(attributedCreds, "CREDENTIALS_CODE", "e");
Copy link
Copy Markdown
Contributor

@kuhe kuhe Jan 5, 2026

Choose a reason for hiding this comment

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

I think this still needs to check that no other attribution exists in $source

@smilkuri smilkuri merged commit 05e017e into main Jan 5, 2026
7 checks passed
@smilkuri smilkuri deleted the feature-id branch January 5, 2026 20:33
@github-actions
Copy link
Copy Markdown

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Jan 20, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants