Right-Size Kubernetes HPA Replica Bounds from Live CPU Utilization
Compare HPA CPU utilization to a target, open a GitHub issue and alert Slack for every replica bound change, then patch with kubectl.
Audit GraphQL schema changes between staging and production via introspection, detect breaking field deletions, and alert teams to prevent API client failures.
Prevent breaking API changes and client application outages by automatically verifying backward compatibility before deploying GraphQL services to production. In agile development teams, engineers frequently delete fields, rename object types, or alter schema contracts during feature refactors without realizing active mobile applications and partner integrations depend on the old schema. This blueprint queries both staging and production GraphQL endpoints via introspection (io.kestra.plugin.graphql.Request), isolates removed types and deleted fields using a Python comparison task, notifies engineering teams via Slack with an itemized diff, and terminates with a pipeline failure to gate downstream CI/CD deployment jobs.
Schedule trigger initiates a preflight verification sweep every weekday morning at 06:00 UTC (shipped disabled by default).fetch_production_schema and task fetch_staging_schema query the live production and candidate staging GraphQL endpoints using io.kestra.plugin.graphql.Request to introspect __schema { types { name kind fields { name args { name } } } }.detect_schema_breaking_changes (io.kestra.plugin.scripts.python.Script) parses both schema payloads, filters out internal introspection types (__Schema, __Type), maps type fields, and flags any fields or types present in production that have been deleted in staging.evaluate_breaking_contract (io.kestra.plugin.core.flow.If) evaluates the breaking change count:alert_breaking_changes posts an itemized Slack alert listing every deleted field and type. If fail_on_breaking_changes is enabled, task halt_deployment_gate fails the execution to prevent production deployment.log_contract_compatible records that the staging schema is clean.log_preflight_summary logs the audit summary.errors handler alerts API Platform engineering if introspection endpoints fail or tokens expire.@deprecated directives instead of hard removals.Standalone schema registry tools often charge heavy per-seat SaaS fees or require complex CLI integrations in every microservice repo. Kestra provides an orchestrator-native, declarative schema comparison gate. With native GraphQL introspection tasks, isolated Python script evaluation, secure secret handling for staging/prod tokens, and rich Slack alerting, Kestra acts as a central governance control plane across all your API services.
GRAPHQL_PROD_TOKEN: Production API access token passed in the Authorization: Bearer header.GRAPHQL_STAGING_TOKEN: Staging API access token passed in the Authorization: Bearer header.SLACK_WEBHOOK_URL: Slack Incoming Webhook URL used to transmit breaking change alerts.GRAPHQL_PROD_TOKEN, GRAPHQL_STAGING_TOKEN, and SLACK_WEBHOOK_URL).staging_graphql_url and production_graphql_url inputs to your service URLs.pre_deployment_audit_schedule trigger or integrate the flow into your deployment pipeline via Webhook trigger.