Revise Deployment
Accept a revision of an applied sftp/v1 deployment and queue a fresh plan (202), the deployment-revision lifecycle (ADR-0027, revised). Add transfer partners (sftp_users, each optionally routed to a destination), add allowed CIDRs, and add ADDITIONAL wired S3 destination buckets; the primary bucket, endpoint_name, and vpc_id are immutable, so a revision is never destructive. The revision re-plans the same deployment; poll GET /deployments/{id} for the plan, then approve to apply the exact reviewed artifact.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Cookie Parameters
Section titled “Cookie Parameters ”Request Body required
Section titled “Request Body required ”Revise an existing sftp/v1 deployment (ADR-0027, revised): the full new params (additive edits, add SFTP users each optionally routed to a destination, add allowed CIDRs) and an optional ADDITIONAL wired S3 destination to add (feeds_into an applied Secure Bucket). Adding a destination is purely additive, the PRIMARY bucket, endpoint_name, and vpc_id are immutable. params validate against the deployment’s template schema; the service enforces the immutable-primary-bucket and additive-only rules and re-plans the same deployment.
object
One blueprint link created with the deployment (ruling R4). direction “feeds_into”: the NEW deployment is the source feeding the named existing deployment; “fed_by”: the named existing deployment feeds the new one.
object
object
Responses
Section titled “ Responses ”Successful Response
object
One blueprint link as seen from THIS deployment: role is the side this deployment plays; other_* describe the deployment at the other end.
object
object
object
object
object
Validation Error