scw config set crashes if there is no config.yaml present

[rickpastoor]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Command attempted

scw config set \
    access-key=*** \
    secret-key=*** \
    default-project-id=*** \
    default-region=nl-ams

I'm running this in Github actions.

Expected Behavior

Config should be set using these four options.

Actual Behavior

scaleway-sdk-go: cannot read config file /home/runner/.config/scw/config.yaml: no such file or directory

[remyleone]

Thanks a lot for opening this issue, it should be available in the next release :)

[Gnoale]

Hello @rickpastoor

Sorry but there was a confusion between SCW_CONFIG_PATH and SCW_CLI_CONFIG_PATH.

you may have seen the change has been rolled back in the latest version,

We will release a proper fix to use SCW_CONFIG_PATH without touching the other cli config which in fact is about aliases and has nothing to do with the credentials.