miro-prod-checklist

name	miro-prod-checklist
description	Execute Miro REST API v2 production deployment checklist and rollback procedures. Use when deploying Miro integrations to production, preparing for launch, or implementing go-live procedures for Miro apps. Trigger with phrases like "miro production", "deploy miro", "miro go-live", "miro launch checklist", "miro production ready".
allowed-tools	Read, Bash(curl:*), Grep
version	1.7.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","miro","production","deployment"]
compatibility	Designed for Claude Code

Miro Production Checklist

Overview

Complete checklist for deploying Miro REST API v2 integrations to production, covering OAuth configuration, rate limit readiness, monitoring, and rollback.

Prerequisites

Before applying this guide, confirm you have a Miro app or workspace appropriate to the task, a dedicated non-production board where changes can be tested safely, and only the OAuth scopes or administrative access the procedure requires.

Pre-Deployment: OAuth & Scopes

• Production Miro app created at https://developers.miro.com (separate from dev app)
• OAuth scopes minimized — only scopes actively used (see miro-security-basics)
• Redirect URI points to production HTTPS endpoint
• Client secret stored in secret manager (not env vars on disk)
• Token refresh logic tested — handles expired tokens gracefully
• Token storage uses encrypted database or vault (not filesystem)

Pre-Deployment: Code Quality

• No hardcoded tokens — scan with grep -r "eyJ\|Bearer " src/
• Error handling covers all Miro HTTP status codes (400, 401, 403, 404, 429, 5xx)
• Rate limiting — backoff with Retry-After header support (see miro-rate-limits)
• Webhook signatures validated with timing-safe comparison
• Pagination handled for all list endpoints (cursor parameter)
• Content-Type header set to application/json on all POST/PATCH requests
• including integration tests against test board