Skip to content

Add stable IDs to webhook mappings - #108

Merged
chrysb merged 2 commits into
mainfrom
codex/openclaw-7-1-webhook-mapping-ids
Jul 17, 2026
Merged

Add stable IDs to webhook mappings#108
chrysb merged 2 commits into
mainfrom
codex/openclaw-7-1-webhook-mapping-ids

Conversation

@chrysb

@chrysb chrysb commented Jul 17, 2026

Copy link
Copy Markdown
Owner

Summary

  • write a stable id on every webhook mapping created or updated by AlphaClaw
  • backfill every missing mapping ID during onboarded startup, before the gateway launches
  • derive readable IDs from path, name, or source, with deterministic mapping-N fallback IDs
  • avoid collisions with existing and newly generated IDs while preserving all existing IDs
  • cover Gmail-style legacy mappings and OAuth-enabled webhook creation

OpenClaw treats mapping IDs as optional and synthesizes positional IDs when absent. This migration makes those identities explicit and stable across reordering, improving diagnostics, auditing, and compatibility for existing user configurations. It is idempotent and requires no manual config edits.

Verification

  • Node.js 22.22.3 full suite on the initial implementation: 102 files, 719 tests passed
  • targeted webhook, OAuth callback, and startup tests pass with collision and fallback coverage
  • git diff --check
  • localhost gateway restarted healthy on OpenClaw 2026.7.1

@chrysb chrysb changed the title Backfill webhook mapping IDs for OpenClaw 7.1 Add stable IDs to webhook mappings Jul 17, 2026
@chrysb
chrysb merged commit 7ed7e9d into main Jul 17, 2026
1 check passed
@chrysb
chrysb deleted the codex/openclaw-7-1-webhook-mapping-ids branch July 17, 2026 01:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant