PostgresqlUser is the Schema for the PostgresqlUsers API. Manages a PostgreSQL user within Yandex.Cloud.
Type
CRD
Group
mdb.yandex-cloud.jet.crossplane.io
Version
v1alpha1
apiVersion: mdb.yandex-cloud.jet.crossplane.io/v1alpha1
kind: PostgresqlUser
PostgresqlUserSpec defines the desired state of PostgresqlUser
No description provided.
Reference to a PostgresqlCluster to populate clusterId.
Policies for referencing.
Selector for a PostgresqlCluster to populate clusterId.
Policies for selection.
List of the user's grants.
Set of permissions granted to the user. The structure is documented below.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
Reference to a PostgresqlCluster to populate clusterId.
Policies for referencing.
Selector for a PostgresqlCluster to populate clusterId.
Policies for selection.
List of the user's grants.
Set of permissions granted to the user. The structure is documented below.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
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.
PostgresqlUserStatus defines the observed state of PostgresqlUser.
No description provided.
List of the user's grants.
Set of permissions granted to the user. The structure is documented below.
Conditions of the resource.
pg-user1
apiVersion: mdb.yandex-cloud.jet.crossplane.io/v1alpha1
kind: PostgresqlUser
metadata:
annotations:
meta.upbound.io/example-id: mdb/v1alpha1/postgresqluser
labels:
testing.upbound.io/example-name: postgres
name: pg-user1
spec:
forProvider:
clusterIdRef:
name: example-pg
connLimit: 50
name: user1
passwordSecretRef:
key: password
name: postgresql
namespace: default
permission: null
settings:
default_transaction_isolation: read committed
log_min_duration_statement: "5000"
providerConfigRef:
name: default