-
Notifications
You must be signed in to change notification settings - Fork 4k
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
fix(rds): circular dependencies when creating multiple DatabaseProxies #28471
fix(rds): circular dependencies when creating multiple DatabaseProxies #28471
Conversation
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
aws#28471) ### Description The related issue reports that deployment fails due to circular dependencies when multiple RDSProxy are created. The `DatabaseProxy` uses the `node.addDependency` method to ensure that the `CfnDBProxyTargetGroup` is created after the `DBCluster` and `DBInstance` are created (aws#12237). This works well for a single `DatabaseProxy`, but does not work well when multiple `DatabaseProxy` are created with `DatabaseCluster.addProxy`. When creating a `DatabaseProxy` with the `DatabaseCluster.addProxy` method, it is created as a child of the `DatabaseCluster`. https://github.com/aws/aws-cdk/blob/cd54c4239ec29182e30fd91634505df560d6e5f8/packages/aws-cdk-lib/aws-rds/lib/cluster.ts#L446 The `node.addDependency` method recursively sets dependencies on child Constructs, so if multiple `DatabaseProxy` are created as a child of a `DatabaseCluster` in the construct tree, multiple `DatabaseProxy` dependencies on each other. If the `addProxy` method is not used, the user initializes the `DatabaseProxy` directly and it does not become a child of `DatabaseCluster`. For example, ```ts new DatabaseProxy(stack, 'DBProxy', { proxyTarget: rds.ProxyTarget.fromCluster(cluster), vpc, }); ``` I believe this is the cause of the `these resources have a dependency cycle` error reported in the related issue. To correct this error, this PR uses `CfnResource.addDependency` instead of `node.addDependency` to avoid recurrent dependencies. Closes aws#25633 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Description
The related issue reports that deployment fails due to circular dependencies when multiple RDSProxy are created.
The
DatabaseProxy
uses thenode.addDependency
method to ensure that theCfnDBProxyTargetGroup
is created after theDBCluster
andDBInstance
are created (#12237).This works well for a single
DatabaseProxy
, but does not work well when multipleDatabaseProxy
are created withDatabaseCluster.addProxy
.When creating a
DatabaseProxy
with theDatabaseCluster.addProxy
method, it is created as a child of theDatabaseCluster
.aws-cdk/packages/aws-cdk-lib/aws-rds/lib/cluster.ts
Line 446 in cd54c42
The
node.addDependency
method recursively sets dependencies on child Constructs, so if multipleDatabaseProxy
are created as a child of aDatabaseCluster
in the construct tree, multipleDatabaseProxy
dependencies on each other.If the
addProxy
method is not used, the user initializes theDatabaseProxy
directly and it does not become a child ofDatabaseCluster
.For example,
I believe this is the cause of the
these resources have a dependency cycle
error reported in the related issue.To correct this error, this PR uses
CfnResource.addDependency
instead ofnode.addDependency
to avoid recurrent dependencies.Closes #25633
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license