Skip to content

fix: handle new tenant api key #3929

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

Merged
merged 1 commit into from
Jul 29, 2025
Merged

fix: handle new tenant api key #3929

merged 1 commit into from
Jul 29, 2025

Conversation

sweatybridge
Copy link
Contributor

@sweatybridge sweatybridge commented Jul 29, 2025

What kind of change does this PR introduce?

Bug fix

What is the new behavior?

CLI should prefer new api key over legacy ones.

Additional context

Add any other context or screenshots.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 16590601734

Details

  • 21 of 36 (58.33%) changed or added relevant lines in 3 files are covered.
  • 7 unchanged lines in 2 files lost coverage.
  • Overall coverage decreased (-0.1%) to 55.256%

Changes Missing Coverage Covered Lines Changed/Added Lines %
internal/utils/tenant/client.go 10 25 40.0%
Files with Coverage Reduction New Missed Lines %
internal/storage/rm/rm.go 2 80.61%
internal/gen/keys/keys.go 5 12.9%
Totals Coverage Status
Change from base Build 16589943609: -0.1%
Covered Lines: 6182
Relevant Lines: 11188

💛 - Coveralls

@sweatybridge sweatybridge merged commit 1cf9098 into develop Jul 29, 2025
14 checks passed
@sweatybridge sweatybridge deleted the api-key branch July 29, 2025 08:45
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.

3 participants