User is the Schema for the Users API. Provides an IAM user.
Type
CRD
Group
iam.aws.upbound.io
Version
v1beta1
apiVersion: iam.aws.upbound.io/v1beta1
kind: User
UserSpec defines the desired state of User
No description provided.
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.
UserStatus defines the observed state of User.
Conditions of the resource.
sample-user-${Rand.RFC1123Subdomain}
apiVersion: iam.aws.upbound.io/v1beta1
kind: User
metadata:
labels:
testing.upbound.io/example-name: group
name: sample-user-${Rand.RFC1123Subdomain}
spec:
forProvider: {}
sample-user-${Rand.RFC1123Subdomain}
apiVersion: iam.aws.upbound.io/v1beta1
kind: User
metadata:
labels:
testing.upbound.io/example-name: user
name: sample-user-${Rand.RFC1123Subdomain}
spec:
forProvider: {}
sample-user-${Rand.RFC1123Subdomain}
apiVersion: iam.aws.upbound.io/v1beta1
kind: User
metadata:
annotations:
meta.upbound.io/example-id: servicecatalog/v1beta1/principalportfolioassociation
uptest.upbound.io/pre-delete-hook: testhooks/delete-user-dependent-resources.sh
labels:
testing.upbound.io/example-name: user
name: sample-user-${Rand.RFC1123Subdomain}
spec:
forProvider: {}
user
apiVersion: iam.aws.upbound.io/v1beta1
kind: User
metadata:
annotations:
meta.upbound.io/example-id: opsworks/v1beta1/userprofile
upjet.upbound.io/manual-intervention: "Need try to use hooks to avoid manual
intervention. This resource needs a service role with next policies
(policies need more time to be attached to the role and we start create
resources without policy attached): AWS OpsWorks Full Access, AWS ECS Full
Access, OpsWorks CM servers, EC2 Full Access, AWS RDS Full Access,
ElasticLoad Balancing Full Access. Also it will be created 17 security
groups when create Stack resource and we cant delete it automatically."
labels:
testing.upbound.io/example-name: user
name: user
spec:
forProvider: {}
test
apiVersion: iam.aws.upbound.io/v1beta1
kind: User
metadata:
annotations:
meta.upbound.io/example-id: cloud9/v1beta1/environmentmembership
labels:
testing.upbound.io/example-name: test
name: test
spec:
forProvider: {}
user
apiVersion: iam.aws.upbound.io/v1beta1
kind: User
metadata:
annotations:
meta.upbound.io/example-id: opsworks/v1beta1/permission
upjet.upbound.io/manual-intervention: "Need try to use hooks to avoid manual
intervention. This resource needs a service role with next policies
(policies need more time to be attached to the role and we start create
resources without policy attached): AWS OpsWorks Full Access, AWS ECS Full
Access, OpsWorks CM servers, EC2 Full Access, AWS RDS Full Access,
ElasticLoad Balancing Full Access. Also it will be created 17 security
groups when create Stack resource and we cant delete it automatically."
labels:
testing.upbound.io/example-name: user
name: user
spec:
forProvider: {}
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.