DOCS-42: Create a collector client (openhound) - #411
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (1)
Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. WalkthroughThe enterprise collection guide now covers SharpHound Enterprise, AzureHound Enterprise, and OpenHound. It adds requirements, client creation steps, API-token details, feature-flag messaging, and ChangesEnterprise collector documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This PR adds OpenHound collector documentation and screenshots without introducing an actionable merge-blocking risk; it is merge-ready after normal checks and review. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
This pull request (PR) adds a new OpenHound section to the Create a collector client docs.
Adding new screenshots for OpenHound made me realize that the SharpHound and AzureHound screenshots also need to be updated since we rolled out some recent UI improvements. That's beyond the scope of this PR.
Summary by CodeRabbit