DeploymentGroup is the Schema for the DeploymentGroups API. Provides a CodeDeploy deployment group.
Type
CRD
Group
deploy.aws.upbound.io
Version
apiVersion: deploy.aws.upbound.io/v1beta1
kind: DeploymentGroup
DeploymentGroupSpec defines the desired state of DeploymentGroup
No description provided.
Configuration block of alarms associated with the deployment group (documented below).
A list of alarms configured for the deployment group. A maximum of 10 alarms can be added to a deployment group.
Reference to a App in deploy to populate appName.
Policies for referencing.
Selector for a App in deploy to populate appName.
Policies for selection.
Autoscaling groups associated with the deployment group.
Configuration block of the blue/green deployment options for a deployment group (documented below).
Information about the action to take when newly provisioned instances are ready to receive traffic in a blue/green deployment (documented below).
Information about how instances are provisioned for a replacement environment in a blue/green deployment (documented below).
Information about whether to terminate instances in the original fleet during a blue/green deployment (documented below).
Configuration block of the type of deployment, either in-place or blue/green, you want to run and whether to route deployment traffic behind a load balancer (documented below).
Configuration block(s) of Tag filters associated with the deployment group, which are also referred to as tag groups (documented below). See the AWS docs for details.
Configuration block(s) of the ECS services for a deployment group (documented below).
Reference to a Cluster in ecs to populate clusterName.
Policies for referencing.
Selector for a Cluster in ecs to populate clusterName.
Policies for selection.
Reference to a Service in ecs to populate serviceName.
Policies for referencing.
Selector for a Service in ecs to populate serviceName.
Policies for selection.
Single configuration block of the load balancer to use in a blue/green deployment (documented below).
The Classic Elastic Load Balancer to use in a deployment. Conflicts with target_group_info and target_group_pair_info.
Reference to a ELB in elb to populate name.
Policies for referencing.
Selector for a ELB in elb to populate name.
Policies for selection.
The (Application/Network Load Balancer) target group to use in a deployment. Conflicts with elb_info and target_group_pair_info.
The (Application/Network Load Balancer) target group pair to use in a deployment. Conflicts with elb_info and target_group_info.
Configuration block for the production traffic route (documented below).
List of Amazon Resource Names (ARNs) of the load balancer listeners.
Configuration blocks for a target group within a target group pair (documented below).
Reference to a LBTargetGroup in elbv2 to populate name.
Policies for referencing.
Selector for a LBTargetGroup in elbv2 to populate name.
Policies for selection.
Configuration block for the test traffic route (documented below).
List of Amazon Resource Names (ARNs) of the load balancer listeners.
Reference to a Role in iam to populate serviceRoleArn.
Policies for referencing.
Selector for a Role in iam to populate serviceRoleArn.
Policies for selection.
Configuration block(s) of the triggers for the deployment group (documented below).
The event type or types for which notifications are triggered. Some values that are supported: DeploymentStart, DeploymentSuccess, DeploymentFailure, DeploymentStop, DeploymentRollback, InstanceStart, InstanceSuccess, InstanceFailure. See the CodeDeploy documentation for all possible values.
Reference to a Topic in sns to populate triggerTargetArn.
Policies for referencing.
Selector for a Topic in sns to populate triggerTargetArn.
Policies for selection.
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.
Configuration block of alarms associated with the deployment group (documented below).
A list of alarms configured for the deployment group. A maximum of 10 alarms can be added to a deployment group.
Autoscaling groups associated with the deployment group.
Configuration block of the blue/green deployment options for a deployment group (documented below).
Information about the action to take when newly provisioned instances are ready to receive traffic in a blue/green deployment (documented below).
Information about how instances are provisioned for a replacement environment in a blue/green deployment (documented below).
Information about whether to terminate instances in the original fleet during a blue/green deployment (documented below).
Configuration block of the type of deployment, either in-place or blue/green, you want to run and whether to route deployment traffic behind a load balancer (documented below).
Configuration block(s) of Tag filters associated with the deployment group, which are also referred to as tag groups (documented below). See the AWS docs for details.
Configuration block(s) of the ECS services for a deployment group (documented below).
Reference to a Cluster in ecs to populate clusterName.
Policies for referencing.
Selector for a Cluster in ecs to populate clusterName.
Policies for selection.
Reference to a Service in ecs to populate serviceName.
Policies for referencing.
Selector for a Service in ecs to populate serviceName.
Policies for selection.
Single configuration block of the load balancer to use in a blue/green deployment (documented below).
The Classic Elastic Load Balancer to use in a deployment. Conflicts with target_group_info and target_group_pair_info.
Reference to a ELB in elb to populate name.
Policies for referencing.
Selector for a ELB in elb to populate name.
Policies for selection.
The (Application/Network Load Balancer) target group to use in a deployment. Conflicts with elb_info and target_group_pair_info.
The (Application/Network Load Balancer) target group pair to use in a deployment. Conflicts with elb_info and target_group_info.
Configuration block for the production traffic route (documented below).
List of Amazon Resource Names (ARNs) of the load balancer listeners.
Configuration blocks for a target group within a target group pair (documented below).
Reference to a LBTargetGroup in elbv2 to populate name.
Policies for referencing.
Selector for a LBTargetGroup in elbv2 to populate name.
Policies for selection.
Configuration block for the test traffic route (documented below).
List of Amazon Resource Names (ARNs) of the load balancer listeners.
Reference to a Role in iam to populate serviceRoleArn.
Policies for referencing.
Selector for a Role in iam to populate serviceRoleArn.
Policies for selection.
Configuration block(s) of the triggers for the deployment group (documented below).
The event type or types for which notifications are triggered. Some values that are supported: DeploymentStart, DeploymentSuccess, DeploymentFailure, DeploymentStop, DeploymentRollback, InstanceStart, InstanceSuccess, InstanceFailure. See the CodeDeploy documentation for all possible values.
Reference to a Topic in sns to populate triggerTargetArn.
Policies for referencing.
Selector for a Topic in sns to populate triggerTargetArn.
Policies for selection.
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.
DeploymentGroupStatus defines the observed state of DeploymentGroup.
No description provided.
Configuration block of alarms associated with the deployment group (documented below).
A list of alarms configured for the deployment group. A maximum of 10 alarms can be added to a deployment group.
Autoscaling groups associated with the deployment group.
Configuration block of the blue/green deployment options for a deployment group (documented below).
Information about the action to take when newly provisioned instances are ready to receive traffic in a blue/green deployment (documented below).
Information about how instances are provisioned for a replacement environment in a blue/green deployment (documented below).
Information about whether to terminate instances in the original fleet during a blue/green deployment (documented below).
Configuration block of the type of deployment, either in-place or blue/green, you want to run and whether to route deployment traffic behind a load balancer (documented below).
Configuration block(s) of Tag filters associated with the deployment group, which are also referred to as tag groups (documented below). See the AWS docs for details.
Configuration block(s) of the ECS services for a deployment group (documented below).
Single configuration block of the load balancer to use in a blue/green deployment (documented below).
The Classic Elastic Load Balancer to use in a deployment. Conflicts with target_group_info and target_group_pair_info.
The (Application/Network Load Balancer) target group to use in a deployment. Conflicts with elb_info and target_group_pair_info.
The (Application/Network Load Balancer) target group pair to use in a deployment. Conflicts with elb_info and target_group_info.
Configuration block for the production traffic route (documented below).
List of Amazon Resource Names (ARNs) of the load balancer listeners.
Configuration blocks for a target group within a target group pair (documented below).
Configuration block for the test traffic route (documented below).
List of Amazon Resource Names (ARNs) of the load balancer listeners.
Configuration block(s) of the triggers for the deployment group (documented below).
The event type or types for which notifications are triggered. Some values that are supported: DeploymentStart, DeploymentSuccess, DeploymentFailure, DeploymentStop, DeploymentRollback, InstanceStart, InstanceSuccess, InstanceFailure. See the CodeDeploy documentation for all possible values.
Conditions of the resource.
example
apiVersion: deploy.aws.upbound.io/v1beta1
kind: DeploymentGroup
metadata:
annotations:
meta.upbound.io/example-id: deploy/v1beta1/deploymentgroup
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
alarmConfiguration:
- alarms:
- my-alarm-name
enabled: true
appNameSelector:
matchLabels:
testing.upbound.io/example-name: example
autoRollbackConfiguration:
- enabled: true
events:
- DEPLOYMENT_FAILURE
ec2TagSet:
- ec2TagFilter:
- key: filterkey1
type: KEY_AND_VALUE
value: filtervalue
- key: filterkey2
type: KEY_AND_VALUE
value: filtervalue
region: us-west-1
serviceRoleArnSelector:
matchLabels:
testing.upbound.io/example-name: example
triggerConfiguration:
- triggerEvents:
- DeploymentFailure
triggerName: example-trigger
triggerTargetArnSelector:
matchLabels:
testing.upbound.io/example-name: example