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

Add project in provider #534

Closed
3 tasks
QuentinBrosse opened this issue Sep 1, 2020 · 4 comments · Fixed by #601
Closed
3 tasks

Add project in provider #534

QuentinBrosse opened this issue Sep 1, 2020 · 4 comments · Fixed by #601

Comments

@QuentinBrosse
Copy link
Contributor

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

Description

A new project feature will be available in public beta soon. We need to add the ability to specify a default project in the Scaleway provider.

New or Affected Resource(s)

  • scaleway

Potential Terraform Configuration

provider "scaleway" {
  access_key      = "<SCALEWAY-ACCESS-KEY>"
  secret_key      = "<SCALEWAY-SECRET-KEY>"
  organization_id = "<SCALEWAY-ORGANIZATION-ID>"
  project_id      = "<SCALEWAY-PROJECT-ID>"
  zone            = "fr-par-1"
  region          = "fr-par"
}

To Do

References

  • #0000
@fredleger
Copy link
Contributor

I don't really get why since the API keys are now scoped to projects this could not be used to auto determine the target project. I did assume so at the first glance so i guess this should be mentioned in the documentation that you need to wait for this issue to be closed if you want to use the provider to provision things inside projects.

@QuentinBrosse
Copy link
Contributor Author

@fredleger you can already provision your resource in a project by setting your project_id in the organization_id field and your project API key in the access_key and secret_key field (it's backward compatible). But yes, this issue will provide cleaner support of Project. :)

I think it's better to provide explicitly the project_id in which you want to provision your resources. It will allow having API keys with custom scopes (only some resources of a project, multiple projects, etc.). This kind of feature is in our roadmap.

fredleger added a commit to fredleger/terraform-provider-scaleway that referenced this issue Sep 29, 2020
Better documentation until scaleway#534 is completed
@fredleger
Copy link
Contributor

@QuentinBrosse Great didn't get that reading the docs. I think it can be wise to mention it until this issue is completed. See PR above.

@QuentinBrosse
Copy link
Contributor Author

@fredleger thanks! 👌

@remyleone remyleone linked a pull request Oct 6, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants