Permission is the Schema for the Permissions API. Provides an OpsWorks permission resource.
Type
CRD
Group
opsworks.aws.upbound.io
Version
v1beta1
apiVersion: opsworks.aws.upbound.io/v1beta1
kind: Permission
PermissionSpec defines the desired state of Permission
No description provided.
Reference to a Stack in opsworks to populate stackId.
Policies for referencing.
Selector for a Stack in opsworks to populate stackId.
Policies for selection.
Reference to a User in iam to populate userArn.
Policies for referencing.
Selector for a User in iam to populate userArn.
Policies for selection.
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.
PermissionStatus defines the observed state of Permission.
No description provided.
Conditions of the resource.
my-stack-permission
apiVersion: opsworks.aws.upbound.io/v1beta1
kind: Permission
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: my_stack_permission
name: my-stack-permission
spec:
forProvider:
allowSsh: true
allowSudo: true
level: iam_only
stackIdSelector:
matchLabels:
testing.upbound.io/example-name: main
userArnSelector:
matchLabels:
testing.upbound.io/example-name: user
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.