add: [microsoft-win11-connection-endpoints] generator for Windows 11 connection endpoints - #379
Merged
Merged
Conversation
…connection endpoints Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0121gk7vaCXX9bMri7tC9XVd
Member
|
Nice one. Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds a new warninglist,
microsoft-win11-connection-endpoints, generated from the two official Microsoft Learn pages listing Windows 11 network endpoints:Unlike the existing hand-maintained
microsoft-win10-connection-endpointslist (frozen since 2022-08-16), this one is backed by a generator (tools/generate-microsoft-win11-endpoints.py) so it can be refreshed automatically going forward.Source choice
Both Learn URLs were probed first with
curl/BeautifulSoup. Both return HTTP 200 with fully server-rendered<table>markup already containing the endpoint data — no JS execution needed. Given that, plainrequests+ BeautifulSoup against the rendered HTML was chosen over falling back to the raw markdown mirror onMicrosoftDocs/windows-itpro-docson GitHub, since the HTML is directly reliable and avoids an extra source/rate-limit dependency.Normalisation
The "Destination" column cells needed cleanup, documented as a comment block at the top of the generator:
<br>-separated multiple endpoints are split.*/*.wildcards are normalised to a leading.to match this repo's existing convention (seemicrosoft-win10-connection-endpoints).*(used inconsistently on the source page, no accompanying footnote found) is stripped as a rendering artifact.Result
152 entries,
type: string, samematching_attributesas the Windows 10 list (domain,hostname,domain|ip).Test plan
generators.loghas no ERROR/WARNING linesjsonschema -i lists/microsoft-win11-connection-endpoints/list.json schema.json— exit 0tools/validate_values.py— exit 0make_list_unique.pyrun; confirmed viagit statusit touched no other tracked listjq -Snormalized, exec bit removedgenerate_all.shupdated next to the other Windows/Microsoft generators (not appended at the end)README.mdindex line inserted in correct alphabetical positionNote: split by the parent session into two PRs (script+generate_all.sh, and list.json+README) — both halves are independently coherent.
🤖 Generated with Claude Code
https://claude.ai/code/session_0121gk7vaCXX9bMri7tC9XVd