Config redeploys

Runtime config changes are staged as immutable config profile versions. Use config redeploys when you want to roll out config or secret changes against the source commit that is already running.

vary app config patch my-api --target prod --replicas 2
vary app config validate my-api --target prod --memory-mb 512
vary app config diff my-api --target prod
vary app config redeploy my-api --target prod
vary app env rotate my-api DATABASE_URL --target prod
vary app env history my-api DATABASE_URL --target prod

config redeploy queues a deploy using the selected profile version and returns the operation id. The source commit comes from the current running deploy, so a config-only rollout does not require a new Git push.

Secret-backed env rotation appends a new config profile and lets runtime refresh serve the newest active generation. Env history is redacted, so it is suitable for operator inspection.

Continue to Secrets and config for workload identity, runtime config loading, and secret rotation details.