---
name: eden-redis-migration
description: Deploy a licensed Eden Redis trial or prepare, resume, validate, and complete an authorized Redis migration through Eden. Use for customer Redis or Redis-compatible endpoints and isolated trial demos.
---

# Eden Redis migration

Help the operator reach a verified Redis migration while keeping the application
serving. Use the operator's chosen artifact, environment, endpoints, and rollout
plan; ask only for a missing decision that changes the next action.

## Choose the starting point

- **Fresh trial:** read [trial.md](references/trial.md), then the bundle's
  `docs/QUICKSTART.md`. This covers Linux Docker hosts, including Azure VMs.
- **Existing deployment or migration:** read
  [migration.md](references/migration.md). Discover and resume the existing
  identities before creating resources.
- **Exact request or response needed:** read only the relevant section of
  [api.md](references/api.md) and the deployment's version-matching API reference.

## Keep the operation bound

Record a redacted checkpoint with artifact digest/version, architecture,
license ID and actual expiry, API origin and authenticated organization,
source and target endpoint IDs/UUIDs, interlay ID/UUID, migration ID/UUID,
workflow run ID if any, latest test-run UUID, phase, evidence time, and the
operator's authorized next actions. Record only identities that exist yet.
Verify these bindings on resume and before a traffic or authority change.
Endpoint names alone do not establish identity or ownership.

Separate the operator's real endpoints from bundle-owned demo fixtures. Never
populate, reset, flush, or delete a customer's database as trial preparation.
A demo request authorizes only the identified demo resources. Provisioning a
cloud database or exposing a listener requires scope from the operator.

## Use the available interface

Use connected Eden tools when available; otherwise use the documented HTTP API
through a local subprocess. No Eden-hosted agent, private model, or cloud
provider is required. Do not configure an LLM endpoint merely to run this skill.
Use the workflow service when supported and requested for guided orchestration;
use direct migration APIs when requested or when workflow support is absent.
Keep one owner for a run; do not start a duplicate workflow to resume it.

An existing deployment does not require a trial bundle or source checkout.
Use its version-matching API documentation. Public starting points are the
[Redis migration walkthrough](https://eden.dev/docs/examples/redis-migration-walkthrough)
and [workflow API reference](https://eden.dev/docs/api/migration-workflows).
Check the installed service's capabilities before using an optional route.
The separate trial bundle is needed only for the fresh-trial path.

Keep secrets out of prompts, command arguments, logs, and checkpoints. Use a
secure endpoint form when available, or operator-owned private request and
authentication files consumed by a subprocess. Return only allowlisted status
and identifiers. Verify TLS normally; use the operator's CA file for custom
trust. Never use insecure TLS to make a failed check pass.

## Execution and cutover

Read current state after a timeout or ambiguous mutation response before any
retry. A successful HTTP response or running test is not completed evidence.
Failed or stale tests, parity failure, unknown delivery, write-log gaps, and
unresolved critical compatibility issues block cutover. Do not use `force`,
blanket acknowledgements, skipped tests, or license changes to bypass a gate.

On expiry, refuse new work and inspect licensing, process, and application-route
state. Runtime-enforced shutdown remains authoritative and must not be bypassed.
Before a manual service stop or restart, verify the authorized application
handoff or approved interruption plan. An expired lease that prevents restart
materially changes a restart plan; do not stop a still-serving deployment merely
to clear the expiry error. Preserve state and obtain qualified continuation.

Before execution, traffic shift, completion, or rollback, tie the exact eligible
action to the reviewed plan and explicit operator authorization. Prior explicit
authorization carries forward for that same current action; do not ask again
merely because a stage finished. A materially changed plan needs a new decision.

After completion, verify terminal migration state, target routing, and application
health. Keep the serving interlay running while applications use it. Stop or
remove it only after a separately authorized, verified application handoff.
Report current identities, evidence, remaining blockers, expiry, and next action.