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 / Add endpoint type provider configuration #2262

Merged
merged 2 commits into from
Jun 8, 2015

Conversation

ggiamarchi
Copy link
Contributor

Add the possibility to specify the endpoint type (public, admin, internal). The default remains the same (public).

Add the possibility to specify the endpoint type
(public, admin, internal). The default remains the
same (public).
@mitchellh
Copy link
Contributor

LGTM!

mitchellh added a commit that referenced this pull request Jun 8, 2015
Openstack / Add endpoint type provider configuration
@mitchellh mitchellh merged commit 27acb45 into hashicorp:master Jun 8, 2015
@hartzell
Copy link
Contributor

hartzell commented Jun 8, 2015

[I'm not sure if I should bring this up here, or file a bug report or if there's a mailing list, or .... I'd appreciate feedback on how the community does this]

After updating this morning, terraform pesters me for two pieces of information that it didn't ask for before:

PUB-0MJ250:nebula-pgperl-builder georgewh$ terraform plan
provider.openstack.api_key
  Enter a value:

provider.openstack.endpoint_type
  Enter a value:

Refreshing Terraform state prior to plan...

It's happy for me to just hit carriage return for both.

I think that the request for the endpoint type is an effect of this change. I haven't tracked down what changed (which commit) to cause it to prompt for the api key.

It's a problem for me to have to hit return to these two questions every time, this should not require manual intervention.

It seems like the logic in openstack/provider's Provider() func seems too simplistic;

  • W.R.T. the endpoint type setting, if I didn't provide it and it's optional, why prompt for it?
  • W.R.T. the api key, there isn't a simple constraint on a single value; one must provide either an api key (via OS_AUTH_TOKEN) or a password (via OS_PASSWORD). I suspect specifying both is an error and specifying neither is an error, which one you would prompt for if neither is specified is a mystery.

@ggiamarchi
Copy link
Contributor Author

@hartzell I don't know why in your situation you get prompted. But waiting for a complete answer you can add -input=false to prevent terraform to ask you anything.

@mitchellh
Copy link
Contributor

Hm, if we set a default value we shouldn't be prompted.

@ghost
Copy link

ghost commented May 2, 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 May 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants