api: list-zones: do not send auth header#90
Draft
natalie-o-perret wants to merge 1 commit intomasterfrom
Draft
Conversation
The /zone endpoint enforces IAM policies on authenticated requests, causing 403 for restricted keys (e.g. DBaaS-only) even though the endpoint returns public data. Skip credentials for list-zones so the call always succeeds.
This was referenced Apr 28, 2026
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
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.
/zoneis public but the server enforces IAM on authenticated requests, so a DBaaS-only key gets 403 for no reason.In
_call_operation, when the operation islist-zones, the request is sent via a plainrequests.requestwithout credentials. No IAM check fires and all zones come back.Snippet used to verify:
Before (master, DBaaS-only key):
After (this branch, same key):
Related: exoscale/egoscale#767, exoscale/exoscale-sdk-java#14
Note
AI-assisted.