Skip to content

chore: respected config precedence for agent-provided secrets#2547

Merged
aryamohanan merged 3 commits into
fix-config-precedencefrom
chore-config-secret-agent
May 13, 2026
Merged

chore: respected config precedence for agent-provided secrets#2547
aryamohanan merged 3 commits into
fix-config-precedencefrom
chore-config-secret-agent

Conversation

@aryamohanan
Copy link
Copy Markdown
Contributor

@aryamohanan aryamohanan commented May 12, 2026

See: #2432 (comment)

Previously, agent-provided secrets configuration was directly applied via secrets.setMatcher(), bypassing the configuration precedence system. This meant agent config would override user-provided config (ENV vars
or in-code config), violating the intended precedence order: ENV > INCODE > AGENT > DEFAULT

The fix follows the established activate pattern used by other modules

@aryamohanan aryamohanan marked this pull request as ready for review May 12, 2026 14:13
@aryamohanan aryamohanan requested a review from a team as a code owner May 12, 2026 14:13
@aryamohanan aryamohanan added the v6 label May 12, 2026
@aryamohanan aryamohanan force-pushed the chore-config-secret-agent branch from d541429 to a735db6 Compare May 13, 2026 08:53
Comment thread packages/core/src/tracing/index.js Outdated
Co-authored-by: kirrg001 <katharina.irrgang@ibm.com>
@sonarqubecloud
Copy link
Copy Markdown

@aryamohanan aryamohanan merged commit 9e5bdef into fix-config-precedence May 13, 2026
3 checks passed
aryamohanan added a commit that referenced this pull request May 14, 2026
---------

Co-authored-by: kirrg001 <katharina.irrgang@ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants