A better fix for #768 too.
Verify-before-activate workflow:
- Deploy as draft —
POST /v1/content/:guid/deploy with activate: false. Returns a bundle ID.
- Hit the preview URL to verify — draft bundles are accessible at
/content/:guid/_bundle:id. The process spins up cold
(MinProcesses=0) on that request, so a successful HTTP response confirms it actually runs.
- Activate —
POST /v1/content/:guid/deploy again with the same bundleId and activate: true. This is what the "Activate Draft" button in the UI does. Only do this if the verify step succeeds. If it does not, we do not activate the bundle. That way, the active bundle should never get a broken build.
A better fix for #768 too.
Verify-before-activate workflow:
POST /v1/content/:guid/deploywithactivate: false. Returns a bundle ID./content/:guid/_bundle:id. The process spins up cold(
MinProcesses=0) on that request, so a successful HTTP response confirms it actually runs.POST /v1/content/:guid/deployagain with the samebundleIdandactivate: true. This is what the "Activate Draft" button in the UI does. Only do this if the verify step succeeds. If it does not, we do not activate the bundle. That way, the active bundle should never get a broken build.