The Scaleway backend currently resolves credentials from:
- Config file (
access-key / secret-key fields)
- Environment variables (
SCW_ACCESS_KEY / SCW_SECRET_KEY)
- Scaleway config file (
~/.config/scw/config.yaml)
Unlike AWS or GCP which have rich native credential chains, Scaleway's options are limited. It would be useful to allow storing the Scaleway access key and secret key in the OS keychain via the system store, and have the Scaleway provider retrieve them from there automatically as a fallback.
Proposed behavior
During Build(), if credentials aren't set via config or environment, try reading them from the SystemStore:
scaleway-access-key -> access keyscaleway-secret-key -> secret key
Users would store them once via:
clef set --store system scaleway-access-key SCWXXXXXXXXXX
clef set --store system scaleway-secret-key xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
This pattern could also be generalized for other providers in the future.
The Scaleway backend currently resolves credentials from:
access-key/secret-keyfields)SCW_ACCESS_KEY/SCW_SECRET_KEY)~/.config/scw/config.yaml)Unlike AWS or GCP which have rich native credential chains, Scaleway's options are limited. It would be useful to allow storing the Scaleway access key and secret key in the OS keychain via the
systemstore, and have the Scaleway provider retrieve them from there automatically as a fallback.Proposed behavior
During
Build(), if credentials aren't set via config or environment, try reading them from theSystemStore:scaleway-access-key-> access keyscaleway-secret-key-> secret keyUsers would store them once via:
This pattern could also be generalized for other providers in the future.