nikita-vanyasin/Calendar Conflicts Reporter

Check for conflicts between on-call schedules and calendar events

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
incident-api-keyincident.io API keyyes
calendar-urlsMulti-line string with URLs of ICS calendar files to check against (one per line)yes
include-schedule-idsMulti-line string with schedule IDs to include (one per line, if empty, include all schedules)no""
exclude-schedule-idsMulti-line string with schedule IDs to exclude (one per line, applied after include filter)no""
reporting-methodReporting method: logs-only, email-ses, slacknologs-only
time-off-patternRegular expression pattern to detect time-off events in calendar summaries and descriptionsnotime off
slack-bot-tokenSlack Bot User OAuth Token (required for slack reporting method)no""
aws-ses-regionAWS region for SES service (required for email-ses reporting method)no""
aws-ses-from-emailFrom email address - must be verified in SES (required for email-ses reporting method)no""
aws-ses-from-nameFrom display name (optional for email-ses reporting method)no""
aws-ses-role-arnIAM role ARN for cross-account access (optional for email-ses reporting method)no""
aws-ses-external-idExternal ID for role assumption (optional for email-ses reporting method)no""
aws-ses-reply-to-emailReply-to email address (optional for email-ses reporting method)no""
log-levelLog level: debug, info, warn, errornoinfo
days-aheadNumber of days ahead to fetch on-call schedulesno30

no outputs