You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did see issues #626 and #1020, but I think this is a bit of a new one.
The documentation shows that one of the parameters is event_hub_authorization_rule_id in the monitor diagnostic setting resource, however, I'm getting this error returned: Error: module.example_kv_diagnostic.azurerm_monitor_diagnostic_setting.azure_mds_log: : invalid or unknown key: event_hub_authorization_rule_id
Thanks for confirming that / apologies for the delayed response here.
Taking a look into this this appears to be a bug in the documentation - the fields are eventhub_authorization_rule_id and eventhub_name (without an underscore between event and hub) - which got renamed during the PR which added support for this but missed in the documentation. I'll open a PR to fix this shortly - but would you be able to take a look and see if using the names without the underscores works for you?
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 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Mar 5, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I did see issues #626 and #1020, but I think this is a bit of a new one.
The documentation shows that one of the parameters is event_hub_authorization_rule_id in the monitor diagnostic setting resource, however, I'm getting this error returned:
Error: module.example_kv_diagnostic.azurerm_monitor_diagnostic_setting.azure_mds_log: : invalid or unknown key: event_hub_authorization_rule_id
This would be my example code
Doing the standard init & apply would reproduce the error.
The text was updated successfully, but these errors were encountered: