feat(tools): add OutageDeck status tool - #6828
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthroughChangesAdds OutageDeck status integration
Sequence Diagram(s)sequenceDiagram
participant Caller
participant OutageDeckStatusTool
participant OutageDeckAPI
Caller->>OutageDeckStatusTool: run or arun with operation and filters
OutageDeckStatusTool->>OutageDeckAPI: GET fixed HTTPS endpoint
OutageDeckAPI-->>OutageDeckStatusTool: provider, service, or incident response
OutageDeckStatusTool-->>Caller: normalized JSON result
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@lib/crewai-tools/src/crewai_tools/tools/outagedeck_status_tool/README.md`:
- Line 32: Update the OutageDeck API documentation hyperlink in the README’s API
description to use the working /developers/api path instead of /docs/api,
preserving the existing tracking parameters and surrounding text.
In `@lib/crewai-tools/tests/tools/outagedeck_status_tool_test.py`:
- Around line 148-157: Update test_service_status_caps_incident_context to
assert the safe_get mock was called with the /api/v1/services/github-actions
endpoint and the expected timeout and redirect settings, confirming the
service_status request contract while preserving the existing normalized-output
assertions.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 5c9d3451-ec4d-4396-8f6f-a45d94d0f212
📒 Files selected for processing (7)
lib/crewai-tools/src/crewai_tools/__init__.pylib/crewai-tools/src/crewai_tools/tools/__init__.pylib/crewai-tools/src/crewai_tools/tools/outagedeck_status_tool/README.mdlib/crewai-tools/src/crewai_tools/tools/outagedeck_status_tool/__init__.pylib/crewai-tools/src/crewai_tools/tools/outagedeck_status_tool/outagedeck_status_tool.pylib/crewai-tools/tests/tools/outagedeck_status_tool_test.pylib/crewai-tools/tool.specs.json
|
Addressed all automated review findings in |
Summary
OutageDeckStatusTooltocrewai-toolsWhy
Infrastructure status changes faster than model knowledge. This gives crews a native, read-only way to inspect current provider and service health without setting up separate vendor parsers, credentials, or an MCP adapter.
Closes #6826
Validation
crewai-toolsrun reached 309 passed and 2 skipped; remaining unrelated tests require optional Oxylabs/Mongo packages or anOPENAI_API_KEYfor existing RAG fixturesAI-authorship disclosure
This PR and its linked issue were authored by an AI agent. GitHub does not grant outside contributors permission to apply upstream labels, so please apply the required
llm-generatedlabel. The same disclosure and label request are public on #6826.