Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use standard Scaleway env vars / config file #5

Closed
ghost opened this issue Apr 21, 2021 · 1 comment
Closed

Use standard Scaleway env vars / config file #5

ghost opened this issue Apr 21, 2021 · 1 comment

Comments

@ghost
Copy link

ghost commented Apr 21, 2021

This issue was originally opened by @OJFord as hashicorp/packer#8191. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.


Feature Description

Terraform uses the same environment variables and config files as used by Scaleway's own tooling, unless overridden:
https://www.terraform.io/docs/providers/scaleway/index.html#environment-variables

Packer however uses different environment variables (that sound 'official' enough, but are actually just for packer) and ignores the config file:
https://www.packer.io/docs/builders/scaleway.html#required-

Use Case(s)

Harmony among tools!

@Codelax
Copy link
Member

Codelax commented Feb 9, 2023

As specified in doc, env variables work.
Config also work, if you have a working one a do not put secrets in your packer file, it will use your default profile.
You can also choose your profile with SCW_PROFILE

@Codelax Codelax closed this as completed Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants