-
Notifications
You must be signed in to change notification settings - Fork 7
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: add new securityGroupNoRuleManagementConflicts rule #108
Conversation
The [docs](https://www.pulumi.com/registry/packages/aws/api-docs/ec2/securitygroup/) have strongly worded note about not using inline rules along with separate security group resources. This PR adds a new rule which will warn the user when they use both together. re pulumi/pulumi-aws#3788
Great to have a test! Code looks good. Waiting on an ack that we can ship this in this repo, similar to my other PR. |
export const securityGroupNoRuleManagementConflicts: StackValidationPolicy = { | ||
name: "security-group-no-rule-management-conflicts", | ||
description: | ||
"Checks that ec2.SecurityGroup resources do not conflict with vpc.SecurityGroupEgressRule, vpc.SecurityGroupIngressRule, or ec2.SecurityGroupRule.\n"+ |
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.
The description gets printed by the CLI output, not sure how good multi-line looks there but probably readable.
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.
LGTM, I'd err on the side of merging. I think we're leaning to this being the right place for the check. but can always move later.
The
docs have strongly worded note about not using inline rules along with separate security group resources. This PR adds a new rule which will warn the user when they use both together.
re pulumi/pulumi-aws#3788