Skip to main content

azure_resource_health_emerging_issues Resource

Use the azure_resource_health_emerging_issues InSpec audit resource to test the properties related to all Azure Resource Health Emerging issues.

Azure REST API Version, Endpoint, and HTTP Client Parameters

This resource interacts with API versions supported by the resource provider. The api_version can be defined as a resource parameter. If not provided, this resource uses the latest version. For more information, refer to the azure_generic_resource document.

Unless defined, this resource uses the azure_cloud global endpoint and default values for the HTTP client. For more information, refer to the resource pack README.

Install

This resource is available in the Chef InSpec Azure resource pack.

For information on configuring your Azure environment for Chef InSpec and creating an InSpec profile that uses the InSpec Azure resource pack, see the Chef InSpec documentation for the Azure cloud platform.

Syntax

An azure_resource_health_emerging_issues resource block returns all Azure Resource Health Emerging issues.

describe azure_resource_health_emerging_issues do
  #...
end

Parameters

This resource does not require any parameters.

Properties

ids
A list of the unique resource IDs.

Field: id

names
A list of names for all the resources.

Field: name

types
A list of types for all the resources.

Field: type

properties
A list of Properties for all the resources.

Field: properties

Note

For information on using filter criteria on plural resources, see the documentation on FilterTable

See Azure’s documentation for other available properties.

Examples

Test that there are emerging health issues that are of lower severity

describe azure_resource_health_emerging_issues.where{ properties.select{|prop| prop.statusActiveEvents.select{ |event| event.severity == 'Warning' } } } do
  it { should exist }
end

Matchers

For a full list of available matchers, see our Universal Matchers page.

This resource has the following special matchers.

exists

# Should not exist if no service health emerging issues are present.

describe azure_resource_health_emerging_issues do
  it { should_not exist }
end

not_exists

# Should exist if the filter returns at least one service health emerging issue.

describe azure_resource_health_emerging_issues do
  it { should exist }
end

Azure Permissions

Your Service Principal must be set up with at least a contributor role on the subscription you wish to test.

Edit this page on GitHub

Thank you for your feedback!

×











Search Results