Provider Args
The provider type for the azurerm package. By default, resources use package-wide configuration settings, however an explicit Provider
instance may be created and passed during resource construction to achieve fine-grained programmatic control over provider settings. See the documentation for more information.
Constructors
Properties
The Azure DevOps Pipeline Service Connection ID.
Base64 encoded PKCS#12 certificate bundle to use when authenticating as a Service Principal using a Client Certificate
The password associated with the Client Certificate. For use when authenticating as a Service Principal using a Client Certificate
The path to the Client Certificate associated with the Service Principal for use when authenticating as a Service Principal using a Client Certificate.
The path to a file containing the Client ID which should be used.
The Client Secret which should be used. For use When authenticating as a Service Principal using a Client Secret.
The path to a file containing the Client Secret which should be used. For use When authenticating as a Service Principal using a Client Secret.
This will disable the x-ms-correlation-request-id header.
The Cloud Environment which should be used. Possible values are public, usgovernment, and china. Defaults to public. Not used and should not be specified when metadata_host
is specified.
The Hostname which should be used for the Azure Metadata Service.
The path to a custom endpoint for Managed Service Identity - in most circumstances this should be detected automatically.
The bearer token for the request to the OIDC provider. For use when authenticating as a Service Principal using OpenID Connect.
The URL for the OIDC provider from which to request an ID token. For use when authenticating as a Service Principal using OpenID Connect.
The path to a file containing an OIDC ID token for use when authenticating as a Service Principal using OpenID Connect.
The set of Resource Providers which should be automatically registered for the subscription.
A list of Resource Providers to explicitly register for the subscription, in addition to those specified by the resource_provider_registrations
property.
Should the AzureRM Provider skip registering all of the Resource Providers that it supports, if they're not already registered?
Should the AzureRM Provider use Azure AD Authentication when accessing the Storage Data Plane APIs?
The Subscription ID which should be used.
Allow Azure AKS Workload Identity to be used for Authentication.