Azure Bucket: anonymous access to public containers is unreachable since #1875

Start in internal/bucket/azure/blob.go at chainCredentialWithSecret and the client-selection path, then inspect auth/azure.NewTokenCredential and the anonymous cases in blob_test.go. Run staticcheck ./internal/... and make test to confirm the control flow and existing coverage. Done means a Bucket without secretRef can reach anonymous access in production, with tests covering that path.

Since #1875 (04ab27b42a4ab3bc989accdd8e958e189c60370c, merged 2025-09-02), a Bucket with provider: azure and no secretRef can no longer get an unauthenticated client. Both paths that would produce one are unreachable on main (99d894dd).

Why

chainCredentialWithSecret appends a credential that is never nil:

https://github.com/fluxcd/source-controller/blob/main/internal/bucket/azure/blob.go#L518

if token := azureauth.NewTokenCredential(ctx, opts...); token != nil {
    creds = append(creds, token)
}

auth/azure.NewTokenCredential returns &tokenCredential{ctx, opts} — a non-nil pointer in a non-nil interface, unconditionally. So the guard is always true, creds is never empty, len(creds) > 0 always holds, and the documented return nil, nil ("If no valid token is created, it returns nil") is dead code.

That propagates to the caller, where token != nil is then always true:

token, err = chainCredentialWithSecret(ctx, o.secret, o.authOpts...)
...
if token != nil {
    c.Client, err = azblob.NewClient(obj.Spec.Endpoint, token, clientOpts)
    return
}

// Fallback to simple client.
c.Client, err = azblob.NewClientWithNoCredential(obj.Spec.Endpoint, clientOpts)  // unreachable

The other unauthenticated path, the o.withoutCredentials early return, is gated on an unexported withoutCredentials() option that is only ever called from blob_test.go (4 call sites) and never from production code. So the anonymous behaviour that tests exercise is reached through a door the reconciler does not have, which is why the tests still pass.

Before #1875 this worked: creds only received NewEnvironmentCredential when that returned non-nil, so an empty chain — and therefore the nil, nil return and the no-credential fallback — was reachable.

Impact

A public/anonymously-readable Azure container configured without a secretRef gets an azblob client carrying a token credential instead of a no-credential client. At request time that calls auth.GetAccessToken, which fails when no Azure identity is configured, so the fetch fails rather than falling back to anonymous access.

I have verified the control flow and the regression point by reading the source; I have not reproduced it against a live public container, so please treat the runtime symptom as inferred from the code path rather than observed.

Found by

staticcheck ./internal/... flags it as SA4023, "this comparison is always true". The repo has no .golangci.yaml and CI runs make test only, so the check does not currently run anywhere.

Possible fixes

• Drop the always-true token != nil guard and decide the chain on whether any credential source is actually configured, so chainCredentialWithSecret can return nil, nil again as documented.
• Or make the intent explicit at the caller and have the reconciler pass the existing withoutCredentials() option when no secretRef is set, which would also give the anonymous path production coverage rather than test-only coverage.

Happy to open a PR for whichever direction you prefer.