Jules Castéran
Jules Castéran
But please note that this is effectively not an issue with our provider but a missing feature in instance api. I've reported it to the relevant team, but I cannot...
It should not have been working with base64, you can use raw while waiting for instance product to add this functionality to its cloudinit datasource. There has been no changes...
As specified in the error message, instance creation request must contain only one of organization or project. You should remove `organization-id="45247b03-7f11-4908-9dc5-94c6d2b0659f"` when adding `project-id="45247b03-7f11-4908-9dc5-94c6d2b0659f"`
It comes from two problems, I created issues to track this, #2579 #2578
Cannot reproduce, feel free to open another issue if you need to. Problem may not be linked to CLI and you can create a ticket on Scaleway if you get...
This is not a CLI problem. Creating a token with access to multiple project will come with IAM. Also, the best way to use multiple projects with different api keys...
Required arguments have changed so request work when setting all of them, but deprecated warning is still printed even tho it is not being used ``` ± scw lb backend...
Forwarded to instance team
Broken config flag has been fix with #2476. It will be included in next release
Also, `scw init secret-key=${secret-key}` will still open interactive prompt to fill access key even tho it is not needed. I will disable this interactive prompt and it should be good