Repository navigation
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 689c904d85
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "This legacy module does not appear to be actively maintained. See documentation/expansion/domaintools.md " | ||
| "for API coverage and the provider-supported MISP integration.\n\n" |
There was a problem hiding this comment.
Publish the referenced DomainTools guide
When the documentation site is built through Makefile, prepare_docs copies only documentation/mkdocs/*.md into the MkDocs source directory, so the new documentation/expansion/domaintools.md guide is never deployed. The generated expansion page therefore directs readers to a repository-relative path that is neither a published page nor a Markdown link; copy/include the guide in the MkDocs build and link to its deployed URL.
Useful? React with 👍 / 👎.
Document the legacy DomainTools module services and maintenance status, distinguish its API coverage from Iris services, and link the provider-supported MISP integration. Update discovery metadata to point readers to the support guide. This change does not alter request or result handling.
Validated the documented lookups against the existing module and ran flake8 on the metadata change. For maintainer review.
Review updates: Publish the support guide through the existing MkDocs source directory and link discovery metadata to its deployed URL.