We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
right now our acceptance tests want to create and delete resources owned by the current user. So they need some way to get the current user.
In the AWS provider, this is handled as https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/caller_identity
No response
data "docker_caller_identity" "current" {} output "username" { value = data.docker_caller_identity.current.username }
None
The text was updated successfully, but these errors were encountered:
provider: add a login data source for getting the current user
3945981
fixes #46 Signed-off-by: Nick Santos <nick.santos@docker.com>
9b85bd4
be7e654
d6e621a
Successfully merging a pull request may close this issue.
Description
right now our acceptance tests want to create and delete resources owned by the current user. So they need some way to get the current user.
In the AWS provider, this is handled as
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/caller_identity
Affected Resource(s) and/or Data Source(s)
No response
Potential Terraform Configuration
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: