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

OpenStack provider does not use OS_USER_DOMAIN_NAME environment variable. #8757

Closed
serialh0bbyist opened this issue Sep 9, 2016 · 3 comments · Fixed by #9725
Closed

OpenStack provider does not use OS_USER_DOMAIN_NAME environment variable. #8757

serialh0bbyist opened this issue Sep 9, 2016 · 3 comments · Fixed by #9725
Labels

Comments

@serialh0bbyist
Copy link

Terraform Version

Terraform v0.7.3

Affected Resource(s)

OpenStack Provider

Expected Behavior

When setting the OS_USER_DOMAIN_NAME environment variable in lieu of OS_DOMAIN_NAME, terraform should not error out, but use the OS_USER_DOMAIN_NAME value.

Actual Behavior

$ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but
will not be persisted to local or remote state storage.

Error refreshing state: 1 error(s) occurred:

* You must provide exactly one of DomainID or DomainName to authenticate by Username

Steps to Reproduce

$ export OS_DOMAIN_NAME=
$ export OS_USER_DOMAIN_NAME="domainname"
$ terraform plan
@jtopjian
Copy link
Contributor

Just a note: this isn't specific with Terraform, but the underlying Gophercloud library. This issue can stay open as a placeholder, but the ultimate fix will be in Gophercloud.

@jtopjian
Copy link
Contributor

Quick update on this: It looks like Gophercloud has everything required for correct v3 authentication and scoping. An upcoming patch will set DomainID and DomainName by checking the following environment variables (in this order):

  • OS_USER_DOMAIN_*
  • OS_PROJECT_DOMAIN_*
  • OS_DOMAIN_*
  • OS_DEFAULT_DOMAIN

@ghost
Copy link

ghost commented Apr 20, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

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

Successfully merging a pull request may close this issue.

3 participants