redeploy_service
Rebuild an existing Git-deployed service from its recorded repository and branch to pick up a new commit; follow the asynchronous call with wait_for_service.
Instructions
Use when: a git app needs a new commit. Asynchronous — follow with wait_for_service.
Re-clones the repository and branch/tag the service was deployed from
and rebuilds it, so picking up a new commit is one call with the service
name alone. Use this instead of ``deploy_git`` when the service already
exists — every coordinate (repo, ref, subdir, private-repo credential
reference) is read back off the service. A service deployed from a
folder/zip has no recorded source and is refused. ``dry_run=True`` returns
the build/config plan diff (env key names only, values never). A
non-dry-run response carries
``summary``, ``hints`` (never empty) and ``next_step`` — the structured
follow-up call.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name of an existing app deployed from Git; its recorded repo, ref, subdir and credential reference are re-read, so no coordinates are passed here. | |
| dry_run | No | true = validate and return the plan (what would change) with zero writes; nothing is built, deployed or audited as a change. | |
| idempotency_key | No | Caller-chosen key: a retry with the same key replays the first result instead of acting twice. Omit and a fresh key is minted per call, so each call acts. |