Skip to content
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(route53resolver): DNS Firewall #15031

Merged
merged 24 commits into from
Aug 31, 2021
Merged

Conversation

jogold
Copy link
Contributor

@jogold jogold commented Jun 8, 2021

Add L2s for FirewallDomainList, FirewallRuleGroup and
FirewallRuleGroupAssociation.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Add L2s for `FirewallDomainList`, `FirewallRuleGroup` and
`FirewallRuleGroupAssociation`.
@gitpod-io
Copy link

gitpod-io bot commented Jun 8, 2021

@njlynch njlynch added effort/medium Medium work item – several days of effort p1 labels Jun 24, 2021
@njlynch njlynch removed their assignment Jun 24, 2021
@jogold
Copy link
Contributor Author

jogold commented Jun 29, 2021

hey @njlynch, i see you removed your assignment here, is someone picking this up? thx

@njlynch
Copy link
Contributor

njlynch commented Jun 29, 2021

Hi @jogold !

is someone picking this up?

Not immediately. Apologies, I should have left a comment along with my unassignment to explain.

We're taking efforts to triage and prioritize issues and PRs more uniformly, and then use a combination of inputs (e.g., 👍s, priority, comments) to decide when to work on both. In tandem, we're also trying to signal and track better what we're actively working on (thus removing my assignment).

I can't give a fixed ETA for when I'll be able to pick this up, but I'll try to carve out time in the next couple weeks. In the meantime, getting folks in the community to 👍 this will help prioritize to show there's a strong interest for these L2s.

njlynch
njlynch previously requested changes Jul 6, 2021
Copy link
Contributor

@njlynch njlynch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! One error message to update and two minor nitpicks. Otherwise is good to go.

Thanks!

packages/@aws-cdk/aws-route53resolver/README.md Outdated Show resolved Hide resolved
Comment on lines 48 to 49
if (!/^[\w-.]{1,128}$/.test(domain)) {
throw new Error(`Invalid domain: ${domain}. The name must have 1-128 characters. Valid characters: A-Z, a-z, 0-9, _, -, .`);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No underscores are allowed in domain names, IIRC, and your regex isn't checking for them.

Suggested change
if (!/^[\w-.]{1,128}$/.test(domain)) {
throw new Error(`Invalid domain: ${domain}. The name must have 1-128 characters. Valid characters: A-Z, a-z, 0-9, _, -, .`);
if (!/^[\w-.]{1,128}$/.test(domain)) {
throw new Error(`Invalid domain: ${domain}. The name must have 1-128 characters. Valid characters: A-Z, a-z, 0-9, -, .`);

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Underscores are unusual but allowed in (sub)domains names and \w includes underscores (\w = [a-zA-Z0-9_])

https://stackoverflow.com/questions/2180465/can-domain-name-subdomains-have-an-underscore-in-it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed the {1,128} part which was incorrect and actually applies to the domain list name.

@mergify mergify bot dismissed njlynch’s stale review July 7, 2021 07:23

Pull request has been modified.

@jogold jogold requested a review from njlynch July 7, 2021 07:41
@jogold
Copy link
Contributor Author

jogold commented Aug 30, 2021

@njlynch can you check this PR again? thx!

@mergify
Copy link
Contributor

mergify bot commented Aug 31, 2021

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: f01ceeb
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit ffdcd94 into aws:master Aug 31, 2021
@mergify
Copy link
Contributor

mergify bot commented Aug 31, 2021

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@jogold jogold deleted the route53resolver-firewall branch August 31, 2021 10:06
TikiTDO pushed a commit to TikiTDO/aws-cdk that referenced this pull request Sep 6, 2021
Add L2s for `FirewallDomainList`, `FirewallRuleGroup` and
`FirewallRuleGroupAssociation`.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
david-doyle-as24 pushed a commit to david-doyle-as24/aws-cdk that referenced this pull request Sep 7, 2021
Add L2s for `FirewallDomainList`, `FirewallRuleGroup` and
`FirewallRuleGroupAssociation`.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-route53resolver effort/medium Medium work item – several days of effort p1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants