-
Notifications
You must be signed in to change notification settings - Fork 237
fix(core): PhZ-resolver-rules #393
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(core): PhZ-resolver-rules #393
Conversation
| @@ -0,0 +1,36 @@ | |||
| # Security Hub Enable Standards | |||
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.
update the documentation
| @@ -0,0 +1,36 @@ | |||
| # Security Hub Enable Standards | |||
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.
update the documentation
src/lib/custom-resources/cdk-associate-hosted-zones/cdk/index.ts
Outdated
Show resolved
Hide resolved
src/lib/custom-resources/cdk-associate-hosted-zones/runtime/src/index.ts
Show resolved
Hide resolved
src/lib/custom-resources/cdk-associate-hosted-zones/runtime/src/index.ts
Show resolved
Hide resolved
src/lib/custom-resources/cdk-associate-resolver-rules/cdk/index.ts
Outdated
Show resolved
Hide resolved
| import { CfnStaticResourcesOutput } from './outputs'; | ||
|
|
||
| // Changing these values will lead to redeploying all Phase-4 RuleAssociation stacks | ||
| const MAX_RESOURCES_IN_STACK = 190; |
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.
Is Resource per stack (190) for rule association correct? Could you please do a cross check
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.
yeah we only need one resource per associating all rules to VPC
| function domainToName(domain: string): string { | ||
| return domain.replace(/\./gi, '-'); | ||
| } | ||
|
|
||
| export function createRuleName(name: string): string { | ||
| const hash = hashPath([name], 8); |
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.
Move these 2 functions to common package so that in future, we can reuse them in other modules
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.