This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

azure_key_vault_secret

attributes

Type: STRUCT
Provider name: properties.attributes
Description: The attributes of the secret.

  • created
    Type: INT64
    Provider name: created
    Description: Creation time in seconds since 1970-01-01T00:00:00Z.
  • enabled
    Type: BOOLEAN
    Provider name: enabled
    Description: Determines whether the object is enabled.
  • exp
    Type: INT64
    Provider name: exp
    Description: Expiry date in seconds since 1970-01-01T00:00:00Z.
  • nbf
    Type: INT64
    Provider name: nbf
    Description: Not before date in seconds since 1970-01-01T00:00:00Z.
  • updated
    Type: INT64
    Provider name: updated
    Description: Last updated time in seconds since 1970-01-01T00:00:00Z.

content_type

Type: STRING
Provider name: properties.contentType
Description: The content type of the secret.

id

Type: STRING
Provider name: id
Description: Fully qualified identifier of the key vault resource.

location

Type: STRING
Provider name: location
Description: Azure location of the key vault resource.

name

Type: STRING
Provider name: name
Description: Name of the key vault resource.

resource_group

Type: STRING

secret_uri

Type: STRING
Provider name: properties.secretUri
Description: The URI to retrieve the current version of the secret.

secret_uri_with_version

Type: STRING
Provider name: properties.secretUriWithVersion
Description: The URI to retrieve the specific version of the secret.

subscription_id

Type: STRING

subscription_name

Type: STRING

tags

Type: UNORDERED_LIST_STRING

type

Type: STRING
Provider name: type
Description: Resource type of the key vault resource.

value

Type: STRING
Provider name: properties.value
Description: The value of the secret. NOTE: ‘value’ will never be returned from the service, as APIs using this model are is intended for internal use in ARM deployments. Users should use the data-plane REST service for interaction with vault secrets.