azure_hpc_cache_skus Resource

Use the azure_hpc_cache_skus InSpec audit resource to test the properties related to all Azure HPC Cache SKUs.

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_hpc_cache_skus resource block returns all Azure HPC Cache SKUs.

describe azure_hpc_cache_skus do
  #...
end

Parameters

Properties

resourceTypes: A resource types list where the SKU applies.

Field: resourceType

names: A list of SKU names.

Field: name

sizes: A list of the SKU sizes.

Field: size

tiers: A tiers list of VM in a scale set.

Field: tier

kind: The supported kind list of resources.

Field: kind

Note

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

Examples

Ensure that there are Standard tier HPC Cache SKUs

describe azure_hpc_cache_skus.where(tier: 'STANDARD') do
  it { should exist }
end

Matchers

This InSpec audit resource has the following special matchers. For a full list of available matchers, please visit our Universal Matchers page.

exists

# Should not exist if no HPC Cache SKUs are present.

describe azure_hpc_cache_skus do
  it { should_not exist }
end
# Should exist if the filter returns at least one HPC Cache SKUs.

describe azure_hpc_cache_skus do
  it { should exist }
end

Azure Permissions

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