terraform-provider-docker
terraform-provider-docker copied to clipboard
Support for registry auth from outside
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
Description
I'm using the Google Cloud container registry which is neatly handled by:
gcloud auth configure-docker
What I'd like to do is piggyback docker_registry_image on top of the assumption that I've already run this command.
New or Affected Resource(s)
docker_registry_image
Potential Terraform Configuration
No major change in current terraform config, this is strictly behavioural.
resource "docker_registry_image" "something" {
name = "gcr.io/my-project/something/something:0.0.0-development"
build {
context = "../docker/something"
}
}
Hi @atrauzzi , as a non-native speaker in English, am I right that piggyback in this context means support? So you'd like the resource to use the auth from gcloud?
According to stoflw the credentials are stored in ~/.config/gcloud/credentials, right? In which format are the credentials stored?
So we would need to parse this file and add it to the auth of the provider.
This issue is stale because it has been open 60 days with no activity.
Remove stale label or comment or this will be closed in 7 days.
If you don't want this issue to be closed, please set the label pinned.
Not stale.