Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: forward merge 'master' into 'v2-main' #15042

Merged
merged 7 commits into from
Jun 14, 2021
Merged

Conversation

aws-cdk-automation
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation commented Jun 9, 2021

Automated action from aws/cdk-ops

otaviomacedo and others added 6 commits June 8, 2021 14:55
…: Access Denied" case (#14986)

Related to #14944

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Since python bundles use source hashes (and as a general best practice), add a recommendation to use a dependency lockfile.

Fixes #14607
Fixes #14895


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
… Cluster (#15012)

Previously, adding/enabling Fargate capacity providers would add the FARGATE and FARGATE_SPOT capacity providers a part of the [capacityProviders field](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-cluster.html#cfn-ecs-cluster-capacityproviders) on the ECS::Cluster resource. However, ASG Capacity Providers can only be specified as part of the [capacityProviders field on the ECS::ClusterCapacityProviderAssociation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-clustercapacityproviderassociations.html#cfn-ecs-clustercapacityproviderassociations-capacityproviders)
resource, due to circular dependency issues.

However, when a cluster is created, any capacity providers regardless of type must all be specified *either* on the cluster *or* as a ClusterCapacityProviderAssociation.  Therefore, in order to support both types on the same cluster, Fargate capacity providers must also be specified as a ClusterCapacityProviderAssociation.

This change removes the Fargate capacity providers from the Cluster resource and adds them as a ClusterCapacityProviderAssociation.

Fixes #14730.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…FargateService props (#14831)

This PR allows the loadbalancer name to be passed to the ApplicationLoadBalancedFargateService. This PR just exposes a prop from the ApplicationLoadBalancer construct.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…4783)

I have the need to pass docker labels to containers created with the ECS Patterns L3 construct.  There wasn't an easy way to add them after construction and passing an entire TaskDefinition seemed suboptimal.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@aws-cdk-automation aws-cdk-automation added pr/auto-approve Notifies the GH action to auto-approve this PR pr/forward-merge PR label to indicate forward merges of master to v2-main pr/no-squash This PR should be merged instead of squash-merging it labels Jun 9, 2021
@gitpod-io
Copy link

gitpod-io bot commented Jun 9, 2021

@aws-cdk-automation
Copy link
Collaborator Author

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: 6dad25a
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit 9ba43c1 into v2-main Jun 14, 2021
@mergify mergify bot deleted the v2/forward-merge-20210609 branch June 14, 2021 16:49
@mergify
Copy link
Contributor

mergify bot commented Jun 14, 2021

Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/auto-approve Notifies the GH action to auto-approve this PR pr/forward-merge PR label to indicate forward merges of master to v2-main pr/no-squash This PR should be merged instead of squash-merging it
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants