api: list-zones: do not send auth header#90
Merged
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
natalie-o-perret
added a commit
to exoscale/egoscale
that referenced
this pull request
Jun 15, 2026
# Description
`/zones` is public but the server enforces IAM on authenticated
requests, so a DBaaS-only key gets 403 for no reason.
`RequestTmpl` now has a `SkipAuth bool` field. When set, the generated
function skips `signRequest` and sends no `Authorization` header.
Operations opt in via `x-skip-auth: true` in the spec, so the guard
survives future regenerations.
**Snippet used to verify:**
```go
package main
import (
"context"
"fmt"
"os"
v3 "github.com/exoscale/egoscale/v3"
"github.com/exoscale/egoscale/v3/credentials"
)
func main() {
creds := credentials.NewStaticCredentials(os.Getenv("EXO_KEY"), os.Getenv("EXO_SECRET"))
client, _ := v3.NewClient(creds)
zones, err := client.ListZones(context.Background())
if err != nil {
fmt.Fprintln(os.Stderr, "error:", err)
os.Exit(1)
}
fmt.Printf("ok: %d zones\n", len(zones.Zones))
}
```
Or with the CLI (DBaaS-only profile, using any command that triggers a
zone switch):
```
# before fix
$ exo dbaas update --valkey-ip-filter 1.2.3.4/32 valkey-test-fix -z de-muc-1
error: unable to create client: switch client zone v3: get zone api endpoint: list zones: ListZones: http response: Forbidden: Forbidden by role policy for compute
# after fix
$ exo dbaas update --valkey-ip-filter 1.2.3.4/32 valkey-test-fix -z de-muc-1
✔ Updating DBaaS Valkey service "valkey-test-fix" 0s
```
**Go before** (master, DBaaS-only key):
```
error: ListZones: http response: Forbidden: Invalid request signature
```
**Go after** (this branch, same key):
```
ok: 8 zones
- ch-gva-2
- ch-dk-2
- at-vie-1
- de-fra-1
- bg-sof-1
- de-muc-1
- at-vie-2
- hr-zag-1
```
Related: exoscale/python-exoscale#90, exoscale/exoscale-sdk-java#14
## Checklist
(For exoscale contributors)
- [x] Changelog updated (under Unreleased block)
---
> [!NOTE]
> AI-assisted.
natalie-o-perret
added a commit
to exoscale/exoscale-sdk-java
that referenced
this pull request
Jun 15, 2026
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.
Add x-skip-auth to the list-zones operation in the spec. The
api.mustache template wraps the signing block in a
{{^vendorExtensions.x-skip-auth}} guard, so the generated
listZonesRequestBuilder omits the Authorization header.
The update workflow injects the extension after fetching the spec,
so the guard survives future automated spec updates. pom.xml now
reads the local api/openapi.yaml instead of fetching the spec at
build time, consistent with the workflow change.
Same fix applied to the Go SDK: exoscale/egoscale#767
Same fix applied to the Python SDK: exoscale/python-exoscale#90
Refs: #14
natalie-o-perret
added a commit
to exoscale/exoscale-sdk-java
that referenced
this pull request
Jun 15, 2026
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.
Add x-skip-auth to the list-zones operation in the spec. The
api.mustache template wraps the signing block in a
{{^vendorExtensions.x-skip-auth}} guard, so the generated
listZonesRequestBuilder omits the Authorization header.
The update workflow injects the extension after fetching the spec,
so the guard survives future automated spec updates. pom.xml now
reads the local api/openapi.yaml instead of fetching the spec at
build time, consistent with the workflow change.
Same fix applied to the Go SDK: exoscale/egoscale#767
Same fix applied to the Python SDK: exoscale/python-exoscale#90
Refs: #14
kobajagi
approved these changes
Jun 16, 2026
natalie-o-perret
added a commit
to exoscale/exoscale-sdk-java
that referenced
this pull request
Jun 16, 2026
`/zone` is public but the server enforces IAM on authenticated requests,
so a DBaaS-only key gets 403 for no reason.
The `api.mustache` template wraps the signing block in a
`{{^vendorExtensions.x-skip-auth}}` guard, so the generated
`listZonesRequestBuilder` sends no `Authorization` header.
The update workflow injects the extension after fetching the upstream
spec, so the guard survives future automated spec updates.
**Snippet used to verify:**
```java
import com.exoscale.sdk.api.ExoscaleApi;
import com.exoscale.sdk.client.ApiClient;
import com.exoscale.sdk.client.Credentials;
import com.exoscale.sdk.model.ListZones200Response;
import com.exoscale.sdk.model.Zone;
Credentials creds = new Credentials(key, secret);
ApiClient apiClient = new ApiClient(creds);
apiClient.updateBaseUri("https://api-ch-gva-2.exoscale.com/v2");
ExoscaleApi api = new ExoscaleApi(apiClient);
ListZones200Response resp = api.listZones();
System.out.printf("ok: %d zones%n", resp.getZones().size());
for (Zone z : resp.getZones()) {
System.out.printf(" - %s%n", z.getName());
}
```
**Before** (main, DBaaS-only key):
```
error 403: {"message":"Invalid request signature"}
```
**After** (this branch, same key):
```
ok: 8 zones
- ch-gva-2
- ch-dk-2
- at-vie-1
- de-fra-1
- bg-sof-1
- de-muc-1
- at-vie-2
- hr-zag-1
```
Related: exoscale/egoscale#767, exoscale/python-exoscale#90
---
> [!NOTE]
> AI-assisted.
Co-authored-by: natalie-o-perret <natalie-o-perret@users.noreply.github.com>
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.
/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.