fix(deadline): change dependency when configuring repository clients … #626
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
configureClientX
methods of theRepository
explicitly add a dependency on theRepository
construct for the client being configured. This caused a circular dependency between the security group of theDeploymentInstance
in theRenderQueue
that configures Deadline Secrets Management and theSecurityGroupIngress
rules created for both the repository file system and the database security groups.This resolves this issue by depending on the installer ASG of
Repository
instead of the entire construct, which removes the dependency on theSecurityGroupIngress
rules mentioned.This change affected the following resources in my synthesized SEP example app:
Dependencies that were removed: (based on my cdk synth of the SEP example)
Dependencies that remain: (based on SEP stack)
Testing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license