Skip to content

Conversation

@thatkookooguy
Copy link
Member

When loadSecrets is called with a class instead of an instance, the refresh manager couldn't update the config object on refresh.

Fix:

  • Add registerConfigInstance() method to VaultIntegration
  • Call it after creating the config instance in initializeVault()
  • Store vaultMetadata for re-registration with the actual instance
  • Re-schedule refreshes with the instance reference

This ensures that when secrets are rotated, the config object is automatically updated with the new values.

@thatkookooguy thatkookooguy force-pushed the feature/fix-vault-register branch from 4c04984 to 73ad851 Compare February 3, 2026 12:59
@codecov
Copy link

codecov bot commented Feb 3, 2026

Codecov Report

❌ Patch coverage is 5.88235% with 16 lines in your changes missing coverage. Please review.
✅ Project coverage is 34.08%. Comparing base (12a47b1) to head (fe94863).
⚠️ Report is 3 commits behind head on beta.

Files with missing lines Patch % Lines
src/vault/vault-integration.ts 0.00% 12 Missing and 4 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             beta      #52      +/-   ##
==========================================
- Coverage   34.36%   34.08%   -0.28%     
==========================================
  Files          11       11              
  Lines        1004     1018      +14     
  Branches      242      246       +4     
==========================================
+ Hits          345      347       +2     
- Misses        601      610       +9     
- Partials       58       61       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

When loadSecrets is called with a class instead of an instance,
the refresh manager couldn't update the config object on refresh.

Fix:
- Add registerConfigInstance() method to VaultIntegration
- Call it after creating the config instance in initializeVault()
- Store vaultMetadata for re-registration with the actual instance
- Re-schedule refreshes with the instance reference

This ensures that when secrets are rotated, the config object is
automatically updated with the new values.
@thatkookooguy thatkookooguy force-pushed the feature/fix-vault-register branch from 73ad851 to fe94863 Compare February 3, 2026 13:35
@thatkookooguy thatkookooguy merged commit 12ab9fa into beta Feb 3, 2026
3 of 4 checks passed
@thatkookooguy thatkookooguy deleted the feature/fix-vault-register branch February 3, 2026 13:37
@github-actions
Copy link

github-actions bot commented Feb 3, 2026

This PR is included in version 2.12.1-beta.2 🎉

The release is available on:

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

This PR is included in version 2.12.2-beta.1 🎉

The release is available on:

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

This PR is included in version 2.12.2 🎉

The release is available on:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant