Add comprehensive API command with resource management by aflanagan · Pull Request #39 · cronitorio/cronitor-cli

aflanagan · 2026-01-28T22:41:07Z

Summary

This PR introduces a new api command that provides full access to the Cronitor API, allowing users to manage monitors, issues, status pages, environments, notifications, and view metrics directly from the CLI.

Key Changes

New API Command Structure

cmd/api.go: Core API command with shared utilities for:
- Request body handling (--data, --file, stdin)
- Output formatting (JSON, table, raw)
- Query parameter building
- Response handling and error parsing

Resource Management Subcommands

cmd/api_monitors.go: Full CRUD operations for monitors with pause/unpause functionality
cmd/api_issues.go: Issue management including create, update, resolve, and delete
cmd/api_environments.go: Environment management for deployment stage separation
cmd/api_notifications.go: Notification list management for alert routing
cmd/api_statuspages.go: Status page creation and management
cmd/api_metrics.go: Monitor metrics and aggregated statistics viewing

API Client Library

lib/api_client.go: Generic HTTP client for Cronitor API with:
- Support for GET, POST, PUT, DELETE, PATCH methods
- Basic authentication using API key
- Query parameter handling
- Response metadata (status code, headers, body)
- JSON formatting and error parsing utilities
- Configurable base URL for dev/production environments

Notable Implementation Details

Flexible Input: Supports JSON data via --data flag, --file flag, or stdin
Output Formats: JSON (default), table, or raw output with optional file writing
Pagination: Built-in support for paginated results via --page flag
Filtering: Common filters like --env, --monitor across commands
Bulk Operations: Monitor creation supports both single and bulk (array) operations
Error Handling: Comprehensive error messages with HTTP status codes and API error parsing
Validation: JSON validation on all inputs before sending to API

Usage Examples

# List monitors
cronitor api monitors

# Get specific monitor with events
cronitor api monitors <key> --with-events

# Create monitor from JSON
cronitor api monitors --new '{"key":"my-job","type":"job"}'

# View metrics as table
cronitor api metrics --monitor <key> --format table

# Pause monitor for 24 hours
cronitor api monitors <key> --pause 24

https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

Implements comprehensive CLI interface for all Cronitor API resources: - monitors: list, get, create, update, delete, pause/unpause - issues: list, get, create, update, delete, bulk operations - statuspages: list, get, create, update, delete - components: list, get, create, update, delete - incidents: list, get, create, update, resolve - metrics: list with time ranges, aggregates - notifications: list, get, create, update, delete - environments: list, get, create, update, delete Features: - Generic API client with proper authentication and error handling - Support for --data and --file flags for JSON input - Support for stdin JSON input via piping - Table and JSON output formats - Pagination support with --page flag - Environment filtering with --env flag - Monitor-specific --with-events flag for latest events - Comprehensive BATS test suite Usage examples: cronitor api monitors cronitor api monitors get <key> cronitor api monitors create --data '{"key":"my-job","type":"job"}' cronitor api issues --state open cronitor api metrics --monitor <key> --aggregates https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

Replace action-word subcommands (list, get, create, update, delete) with a cleaner flag-based pattern inspired by Vercel and Sentry CLIs: - `cronitor api monitors` lists all monitors - `cronitor api monitors <key>` gets a specific monitor - `cronitor api monitors --new '{...}'` creates a new monitor - `cronitor api monitors <key> --update '{...}'` updates a monitor - `cronitor api monitors <key> --delete` deletes a monitor Applied consistently across all API resources: monitors, issues, statuspages, components, incidents, notifications, and environments. https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

Incidents are the same as issues, and components are part of status pages rather than standalone API resources. https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

Replace `cronitor api <resource>` with `cronitor <resource> <action>`: cronitor monitor list cronitor monitor get <key> cronitor monitor create --data '{...}' cronitor monitor update <key> --data '{...}' cronitor monitor delete <key> cronitor monitor pause <key> cronitor monitor unpause <key> Same pattern for: statuspage, issue, notification, environment Features: - Beautiful table output using lipgloss styling - Colored status indicators (passing/failing/paused) - Consistent --format, --output, --page flags - Aliases: `env` for environment, `notifications` for notification https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

- Create internal/testutil package with shared MockAPI server, CaptureStdout helper, and ExecuteCommand helper for command-level testing - Refactor lib/api_client_test.go to use shared testutil package - Add MergePagedJSON and FetchAllPages unit tests in cmd/ui_test.go - Add integration tests in cmd/integration_test.go covering table, JSON, YAML output formats, file output, pagination metadata, and --all flag - Add API documentation URLs to all resource command help text Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Run `go test ./...` on both Linux and Windows before the BATS integration tests. All Go tests use mock servers and need no secrets. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

…bility - Inject key into PUT request body for all update commands (environment, group, issue, notification, maintenance, site, statuspage, component) - Fix issue resolve to fetch current issue before PUT (API requires all fields) - Fix JSON response key mismatches: issue, maintenance, site, statuspage, and component list commands used wrong keys (e.g. "issues" vs "data") - Fix statuspage list subdomain field ("subdomain" → "hosted_subdomain") - Update test fixtures to match actual API response structure Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

Document search, clone, bulk delete, YAML support, components, bulk issue actions, and additional filter flags. https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

…spages The --all flag could result in fetching hundreds of pages for high-volume resources like issues. Keep --all only on monitors where accounts typically have ~500 monitors max (~18 pages). Add integration tests for monitor list --all that run when CRONITOR_API_KEY is available on CI. https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

The --all flag is not the right approach for any resource. Users can paginate explicitly with --page. Replace --all example with --format yaml to highlight YAML config export capability. https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

- convertWeekOfMonth: Replace map iteration with ordered slices to ensure deterministic output order (Go maps iterate randomly) - TimeTrigger: Add description "Runs once at <time>" instead of returning empty description - TestCompleteScenario_StartupTask: Fix string length check from 13 to 19 to match "Runs on system boot" (19 chars) https://claude.ai/code/session_01XhBKxwYS2NYdHX7KsuTZHn

TimeTrigger is a one-time trigger that intentionally returns no description. Remove the test case that incorrectly expected one rather than changing production code to satisfy it. https://claude.ai/code/session_01XhBKxwYS2NYdHX7KsuTZHn

https://claude.ai/code/session_01XhBKxwYS2NYdHX7KsuTZHn

Replace the --all flag with dedicated export subcommands: - `cronitor monitor export` - exports all monitors as YAML config (uses two-pass: JSON for page count, then YAML for each page) - `cronitor group export` - exports all groups as JSON Remove --all from maintenance, site, and all other list commands. Add groups section to README documentation. https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

claude and others added 16 commits February 5, 2026 02:21

API - Remove incidents and components (not separate resources)

77aa63f

Incidents are the same as issues, and components are part of status pages rather than standalone API resources. https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

Add Go test step to CI workflow

8ecd48a

Run `go test ./...` on both Linux and Windows before the BATS integration tests. All Go tests use mock servers and need no secrets. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

README - Document API resource commands

9840c62

https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

README - Update API docs to reflect enhanced commands

392e9c3

Document search, clone, bulk delete, YAML support, components, bulk issue actions, and additional filter flags. https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

Add standalone TimeTrigger test asserting no RRULE and no description

55098b3

https://claude.ai/code/session_01XhBKxwYS2NYdHX7KsuTZHn

Remove group export command (monitor export --group covers this)

ecb79c4

https://claude.ai/code/session_01UDueW9A6SuxugCcsbAMfdB

aflanagan force-pushed the claude/cronitor-api-support-PLatz branch from f17f938 to ecb79c4 Compare February 5, 2026 02:22

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add comprehensive API command with resource management#39

Add comprehensive API command with resource management#39
aflanagan wants to merge 16 commits intomasterfrom
claude/cronitor-api-support-PLatz

aflanagan commented Jan 28, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

aflanagan commented Jan 28, 2026

Summary

Key Changes

New API Command Structure

Resource Management Subcommands

API Client Library

Notable Implementation Details

Usage Examples

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants