Project: Chef InSpec (Provisioning / Security & Compliance)
File: azurerm_event_hub_authorization_rule.md

+++ title = "azurermeventhubauthorizationrule resource" draft = false gh_repo = "inspec" platform = "azure" [menu] [menu.inspec] title = "azurermeventhubauthorizationrule" identifier = "inspec/resources/azure/azurermeventhubauthorizationrule.md azurermeventhubauthorizationrule resource" parent = "inspec/resources/azure" +++ {{< inspec/azurermdeprecated resource="azureeventhubauthorization_rule" >}} Use the `azurermeventhubauthorizationrule` InSpec audit resource to test properties and configuration of an Azure Event Hub Authorization Rule within a Resource Group. This resource interacts with version `2017-04-01` of the Azure Management API. For more information see the . At the moment, there doesn't appear to be a way to select the version of the Azure API docs. If you notice a newer version being referenced in the official documentation please open an issue or submit a pull request using the updated version. This resource is available in the `inspec-azure` [resource pack](/inspec/glossary/#resource-pack). To use it, add the following to your `inspec.yml` in your top-level profile: depends: inspec-azure: git: https://github.com/inspec/inspec-azure.git You'll also need to setup your Azure credentials; see the resource pack . This resource first became available in 1.11.0 of the inspec-azure resource pack. The `resourcegroup`, `namespacename`, `eventhubname` and `authorizationrulename` must be given as a parameter. describe azurermeventhubauthorizationrule(resourcegroup: 'my-rg', namespacename 'event-hub-namespace', eventhubname: 'event-hub', authorizationrulename: 'my-auth-rule') do it { should exist } end If an Event Hub Authorization Rule is referenced with a valid `Resource Group`, `Namespace Name`, `Event Hub Name` and `Authorization Rule Name` describe azurermeventhubauthorizationrule(resourcegroup: 'my-rg', namespacename: 'event-hub-namespace', eventhubendpoint: 'event-hub', authorization_rule: 'my-auth-rule') do it { should exist } end If a Event Hub Authorization Rule is referenced with an invalid `Resource Group`, `Namespace Name`, `Event Hub Name` or `Authorization Rule Name` describe azurermeventhubnamespace(resourcegroup: 'invalid-rg', namespacename: 'i-do-not-exist', eventhubendpoint: 'fake-endpoint', authorizationrule: 'fake-auth-rule') do it { should_not exist } end `resource_group` - The resource Group to which the Event Hub Namespace belongs. `namespace_name` - The unique name of the Event Hub Namespace. `eventhubname` - The unique name of the Event Hub Name. `authorizationrulename` - The unique name of the Event Hub Authorization Rule. `id` `name` `properties.rights` `type` Azure resource ID. Event Hub Authorization Rule name, e.g. `my-auth-rule`. A collection of additional configuration properties related to the Event Hub Authorization Rule, eg. `rights` The type of Resource, typically `Microsoft.EventHub/Namespaces/EventHubs/AuthorizationRules`. There are additional attributes that may be accessed that we have not documented. Please take a look at the . Any attribute in the response may be accessed with the key names separated by dots (`.`). The API may not always return keys that do not have any associated data. There may be cases where the deeply nested property may not have the desired attribute along your call chain. If you find yourself writing tests against properties that may be nil, fork this resource pack and add an accessor to the resource. Within that accessor you'll be able to guard against nil keys. Pull requests are always welcome. {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. describe azurermeventhubauthorizationrule(resourcegroup: 'my-rg', namespacename 'event-hub-namespace', eventhubname: 'event-hub', authorizationrulename: 'my-auth-rule') do it { should exist } end Your [Service Principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) must be setup with a `contributor` role on the subscription you wish to test.