Idempotent gateway sync: adopt on conflict, paginate for real, and never widen scope

Short summary

Kong gateway syncs must be idempotent converge operations, not one-shot creates. Three key patterns: handle 409 UNIQUE conflicts by adopting existing records instead of failing the sync, paginate through all API results with cursor following instead of assuming page 1 contains everything, and preserve scope as core record identity to prevent scoped plugins from silently becoming global. The idempotency principle: running the sync twice should always be safe and produce a no-op on the second run.

• •Treat 409 UNIQUE conflicts as 'already exists, adopt it' rather than sync failure
• •Paginate fully through API results following cursors to avoid false orphan deletion
• •Never let scoped plugins silently become global—scope is part of record identity

Generated with AI, which can make mistakes.