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

Managing API keys #6413

Closed
shouichi opened this issue May 19, 2020 · 2 comments
Closed

Managing API keys #6413

shouichi opened this issue May 19, 2020 · 2 comments

Comments

@shouichi
Copy link

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 "me too" comments, 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. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

It seems like we can not manage API keys. We need to manage them to use Google Maps' geocoding API that requires an API key.

New or Affected Resource(s)

  • API Keys

Potential Terraform Configuration

# Propose what you think the configuration to take advantage of this feature should look like.
# We may not use it verbatim, but it's helpful in understanding your intent.

resource "google_api_key" "key" {
	api_restrictions = [
		"geocoding",
		...,
	]
}

References

@emilymye
Copy link
Contributor

In general, API keys with Google Cloud or other Google APIs are not creatable via Terraform because they only can be created via the Cloud Console UI/web-app, not programatically using some API, and they tend to require OAuth2 authentication to create (i.e. your Google login), which we don't support in Terraform.

I'm also not sure that this is a good idea anyways, since API keys for Google APIs tend to be long-lasting, identifying credentials specific to a user or group of users (human operators), and thus should be bootstrapped and managed like other root secrets rather than service account keys or other secrets, which were meant to be used by machines or programatically created/deleted (even if they are also long-lasting and identifying in practice :( )

@ghost
Copy link

ghost commented Jun 26, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Jun 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants