Harden the authentication flow (prefer Qovery API over token creation) - #9
Closed
jpetitcolas wants to merge 2 commits into
Closed
Harden the authentication flow (prefer Qovery API over token creation)#9jpetitcolas wants to merge 2 commits into
jpetitcolas wants to merge 2 commits into
Conversation
evoxmusic
approved these changes
May 7, 2026
Contributor
|
@jpetitcolas you need to have GPG signature and sign your commits (it's a requirement enforced by our security team) |
jpetitcolas
force-pushed
the
fix/auth-prefer-qovery-api
branch
2 times, most recently
from
May 7, 2026 15:30
dbc9198 to
03f6d95
Compare
Restructures _shared/auth.md into 4 tiers checked in order: 1. qovery api (CLI-mediated, no token exposure) 2. env token (QOVERY_API_TOKEN / QOVERY_CLI_ACCESS_TOKEN) 3. JWT fallback (~/.qovery/context.json — for restricted-role users) 4. Interactive login Replaces the previous token-printing flow (qovery auth token --print piped into curl) with qovery api as the default. The CLI authenticates internally so no secret needs to enter the agent's command stream. Tiers 2/3 remain for edge cases (env-only contexts, read-only roles).
…reminder Each phase1 'Authenticate' subsection now points at qovery api as the preferred path and references the auth doc (already loaded via the skill nav) for fallback tiers. Avoids per-skill drift while keeping the section self-contained — no chained reference indirection.
jpetitcolas
force-pushed
the
fix/auth-prefer-qovery-api
branch
from
May 7, 2026 15:44
03f6d95 to
e094c39
Compare
Author
|
Superseded by #10 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcomes
Eliminates token exposure risk and aligns the auth flow with how the Qovery CLI actually works:
qovery api /organizationalready carries the user's session, so there is no need to create a named token during skill execution. Skills now work cleanly for users with restricted roles who cannot create tokens.Preview
Before:
The skill tries to read the tokens right from the environment, exposing the token into the LLM context.
After:
We rely exclusively on the
qoveryCLI, not exposing anything to the LLM.Technical Changes
_shared/auth.mdand all synced copies: CLI (qovery api) → env token → JWT fallback → interactive loginqovery contexttoqovery api /organization— a real API round-trip that confirms the CLI is authenticated and reachablereference/auth.mdinstead of repeating inline auth steps