Skip to content

fix: fall back to profile project when Account API is unavailable - #8

Merged
Andarius merged 1 commit into
masterfrom
fix/project-api-fallback
Jun 3, 2026
Merged

fix: fall back to profile project when Account API is unavailable#8
Andarius merged 1 commit into
masterfrom
fix/project-api-fallback

Conversation

@Andarius

@Andarius Andarius commented Jun 3, 2026

Copy link
Copy Markdown
Owner

Summary

  • API keys scoped only to Secret Manager lack ProjectManager:ListProjects permission, so getProjects returns 403
  • Previously the UI surfaced this as "insufficient permissions" and cleared the project/secret state entirely
  • Now falls back to the profile's default_project_id as a synthetic "Default Project" entry, so secrets continue to load for narrowly-scoped keys

Test plan

  • Configure an API key that has Secret Manager permissions but not Account API permissions
  • Select that profile in the UI — project dropdown should show "Default Project" and secrets should load normally
  • Confirm no error banner is shown
  • Confirm profiles with full Account permissions still list all projects as before

API keys scoped only to Secret Manager lack `ProjectManager:ListProjects`
permission, causing `getProjects` to return 403. The UI previously surfaced
this as "insufficient permissions" and cleared the project/secret state.

Fall back to the profile's `default_project_id` as a synthetic project entry
so secrets continue to load for narrowly-scoped API keys.
@Andarius
Andarius merged commit a8c53a1 into master Jun 3, 2026
1 check passed
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