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

New Data Source: azurerm_eventhub_namespace #673

Merged
merged 4 commits into from
Jan 9, 2018

Conversation

tombuildsstuff
Copy link
Contributor

Tests pass:

$ acctests azurerm TestAccDataSourceAzureRMEventHubNamespace_
=== RUN   TestAccDataSourceAzureRMEventHubNamespace_basic
--- PASS: TestAccDataSourceAzureRMEventHubNamespace_basic (264.97s)
=== RUN   TestAccDataSourceAzureRMEventHubNamespace_complete
--- PASS: TestAccDataSourceAzureRMEventHubNamespace_complete (327.02s)
PASS
ok  	github.com/terraform-providers/terraform-provider-azurerm/azurerm	592.023s

Tests pass:
```
$ acctests azurerm TestAccDataSourceAzureRMEventHubNamespace_
=== RUN   TestAccDataSourceAzureRMEventHubNamespace_basic
--- PASS: TestAccDataSourceAzureRMEventHubNamespace_basic (264.97s)
=== RUN   TestAccDataSourceAzureRMEventHubNamespace_complete
--- PASS: TestAccDataSourceAzureRMEventHubNamespace_complete (327.02s)
PASS
ok  	github.com/terraform-providers/terraform-provider-azurerm/azurerm	592.023s
```
Copy link
Member

@mbfrahry mbfrahry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with just a minor comment


keys, err := client.ListKeys(resourceGroup, name, eventHubNamespaceDefaultAuthorizationRule)
if err != nil {
log.Printf("[ERROR] Unable to List default keys for EventHub Namespace %q (Resource Group %q): %+v", name, resourceGroup, err)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this worth error-ing out completely instead of just logging? The ERROR makes it seem like it's an issue instead of keys just not being there. Might be worth swapping to an INFO or WARN tag.

Copy link
Contributor Author

@tombuildsstuff tombuildsstuff Jan 9, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good shout - I'll update this to a WARN 👍

erroring out completely doesn't make sense since it's valid that a user may have permissions to the EventHub but not the keys (AFAIK)

@tombuildsstuff tombuildsstuff removed the request for review from paultyng January 9, 2018 09:46
@tombuildsstuff tombuildsstuff merged commit fdec84c into master Jan 9, 2018
@tombuildsstuff tombuildsstuff deleted the eventhub-namespaces-data-source branch January 9, 2018 10:05
tombuildsstuff added a commit that referenced this pull request Jan 9, 2018
@ghost
Copy link

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

Successfully merging this pull request may close these issues.

2 participants