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

Add Github workflow to check _psl DNS entries on PRs #1933

Merged
merged 1 commit into from
May 24, 2024

Conversation

simon-friedberger
Copy link
Contributor

Let's have more automatic checks!

@weppos
Copy link
Member

weppos commented Feb 19, 2024

Hi @simon-friedberger, can you provide a bit more context about this PR. Is there a conversation somewhere about it? What's the purpose of this script, and what is the expectation?

I also wonder, I see it was developed in Python. Is it because that's the language you are most familiar with, or is there another reason? I am asking as we had Python code in the past but it was not really the most preferred language and we moved most of the tooling to Go. I am a bit concerned about adding more Python again, for the long term maintainability.

@dnsguru
Copy link
Member

dnsguru commented Feb 19, 2024 via email

@simon-friedberger
Copy link
Contributor Author

I am not against using Go for this if that is the project preference. Python was just the natural choice for me.

@dnsguru
Copy link
Member

dnsguru commented Feb 19, 2024

I am not against using Go for this if that is the project preference. Python was just the natural choice for me.

Same thought, as go is less familiar to me, but want to minimize complexity with >1 approaches at this point so we don't add interop burdens

@simon-friedberger
Copy link
Contributor Author

The submission by Sam here is also in Python and @dnsguru has expressed support. Can I go ahead with this?

@dnsguru
Copy link
Member

dnsguru commented May 2, 2024

After discussion, this looks like a good idea - accompanied by test suite elements to know about impacts. The automation work is really appreciated

@dnsguru
Copy link
Member

dnsguru commented May 2, 2024

I suggested a TLD and TLD w a sld wildcard in the examples for the test suite

I was also thinking of IDN support. Upon some contemplation, I believe IDN scenarios would function identically to their LDH equivelents in the test suite. Just documenting here that IDN was considered. Adding them here would be placebo; cosmetic-only, require additional dependencies/libraries/modules, add complexity and not have any difference in outcome, so would not deliver any value or benefit in exchange for the overhead.

@dnsguru dnsguru added the non .dat Change or Coding Review Alteration to code/automation or publicsuffix.org site label May 2, 2024
@simon-friedberger
Copy link
Contributor Author

As soon as I get to it we should merge this with parsing and checks for individual rules in the linter here https://github.com/publicsuffix/list/blob/master/linter/pslint.py that should cover IDN issues.

@simon-friedberger
Copy link
Contributor Author

@weppos Please have a look!

@simon-friedberger simon-friedberger merged commit c2f7b43 into publicsuffix:master May 24, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
non .dat Change or Coding Review Alteration to code/automation or publicsuffix.org site
Projects
Status: Done or Won't
Development

Successfully merging this pull request may close these issues.

3 participants