AccessPolicy is the Schema for the AccessPolicys API. Manages a Key Vault Access Policy.
Type
CRD
Group
keyvault.azure.upbound.io
Version
v1beta1
apiVersion: keyvault.azure.upbound.io/v1beta1
kind: AccessPolicy
AccessPolicySpec defines the desired state of AccessPolicy
No description provided.
List of certificate permissions, must be one or more from the following: Backup, Create, Delete, DeleteIssuers, Get, GetIssuers, Import, List, ListIssuers, ManageContacts, ManageIssuers, Purge, Recover, Restore, SetIssuers and Update.
List of key permissions, must be one or more from the following: Backup, Create, Decrypt, Delete, Encrypt, Get, Import, List, Purge, Recover, Restore, Sign, UnwrapKey, Update, Verify and WrapKey.
Reference to a Vault to populate keyVaultId.
Policies for referencing.
Selector for a Vault to populate keyVaultId.
Policies for selection.
List of secret permissions, must be one or more from the following: Backup, Delete, Get, List, Purge, Recover, Restore and Set.
List of storage permissions, must be one or more from the following: Backup, Delete, DeleteSAS, Get, GetSAS, List, ListSAS, Purge, Recover, RegenerateKey, Restore, Set, SetSAS and Update.
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
AccessPolicyStatus defines the observed state of AccessPolicy.
No description provided.
Conditions of the resource.
server
apiVersion: keyvault.azure.upbound.io/v1beta1
kind: AccessPolicy
metadata:
annotations:
upjet.upbound.io/manual-intervention: The resource depends on a Server and it needs a manual intervention.
labels:
testing.upbound.io/example-name: server
name: server
spec:
forProvider:
keyPermissions:
- Get
- UnwrapKey
- WrapKey
keyVaultIdSelector:
matchLabels:
testing.upbound.io/example-name: example
objectId: ${azurerm_postgresql_server.example.identity.0.principal_id}
secretPermissions:
- get
tenantId: ${data.azurerm_client_config.current.tenant_id}
example
apiVersion: keyvault.azure.upbound.io/v1beta1
kind: AccessPolicy
metadata:
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
certificatePermissions:
- Get
- GetIssuers
- SetIssuers
- Import
keyPermissions:
- Get
- Create
keyVaultIdSelector:
matchLabels:
testing.upbound.io/example-name: example
objectId: ${data.azurerm_client_config.current.object_id}
secretPermissions:
- Get
- Set
- Delete
storagePermissions:
- Get
- List
- Set
- SetSAS
- GetSAS
- DeleteSAS
- Update
- RegenerateKey
tenantId: ${data.azurerm_client_config.current.tenant_id}
example-user
apiVersion: keyvault.azure.upbound.io/v1beta1
kind: AccessPolicy
metadata:
labels:
testing.upbound.io/example-name: example-user
name: example-user
spec:
forProvider:
keyPermissions:
- Get
- Create
- Delete
keyVaultIdSelector:
matchLabels:
testing.upbound.io/example-name: example
objectId: ${data.azurerm_client_config.current.object_id}
tenantId: ${data.azurerm_client_config.current.tenant_id}
providerConfigRef:
name: default
client
apiVersion: keyvault.azure.upbound.io/v1beta1
kind: AccessPolicy
metadata:
annotations:
upjet.upbound.io/manual-intervention: The resource depends on a Server and it needs a manual intervention.
labels:
testing.upbound.io/example-name: client
name: client
spec:
forProvider:
keyPermissions:
- Get
- Create
- Delete
- List
- Restore
- Recover
- UnwrapKey
- WrapKey
- Purge
- Encrypt
- Decrypt
- Sign
- Verify
keyVaultIdSelector:
matchLabels:
testing.upbound.io/example-name: example
objectId: ${data.azurerm_client_config.current.object_id}
secretPermissions:
- Get
tenantId: ${data.azurerm_client_config.current.tenant_id}
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.