Apply batch

POSThttps://api.instacloud.com/projects/{projectId}/apply

Token scope: account · org · project — read-only tokens refused (not a GET).

Write a batch of user secrets, then redeploy the compute services those values reach, one deploy per service. Entries are reported written individually and services are reported deployed, started, skipped or failed individually, because the writes commit before the deploys run and a failed deploy never rolls a value back. skipDeploy writes without deploying. excludeFromDeploy drops services the caller is deploying itself; deployOnly names the services to deploy and ignores derivation, which is how a failed deploy is retried with no entries. A rename writes no env, so it deploys nothing on its own and needs no deploy grant — a batch that both renames and writes still deploys, for the write. Gated on what the body contains: secrets.write for any set or delete, service.rename for a rename, deploy only for what can actually deploy. A project-scoped entry is authorized against every branch, since that is where its value lands. Deploying a stopped service starts it. A suspended service is skipped instead of deployed: a deploy would invalidate the RAM snapshot suspension exists to preserve, so it is left untouched and reported with reason suspended.

Parameters

Request body

application/json

Responses

View as Markdown