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.
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
feat(ec2): lookup security group by name #17246
feat(ec2): lookup security group by name #17246
Changes from 2 commits
463e599
927ba53
a168099
f24916e
379dac8
a1ca5d8
aca049c
6f85178
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about dedicated
fromLookupById
andfromLookupByName
methods? They could both still use a (private)fromLookupAttributes
method, but it may make the API intent a bit more clear.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried to create an API similar to VpcLookupOptions. Now I compared it to
fromLookupById
andfromLookupByName
again. For me, this seems to be a better option because the necessary parameters are defined by the API. I've implemented the following changes:fromLookup
, will be replaced byfromLookupById
(same parameters).fromLookupById
with parametersecurityGroupId
. Parametervpc
not defined because the security group id is sufficient to clearly identify the security group.fromLookupByName
with parameterssecurityGroupName
andvpc
.vpc
is defined as required parameter because it avoids problems if the same security group name is used multiple times per account and region. A security group is used in context of a VPC. Therefore, the VPC should be available in the CDK code. If it should be defined as optional later, we could changed it easily (no breaking change).