Context
Found during React on Rails 17.1.0.rc.1 fleet validation (shakacode/react_on_rails#4842, pack fleet-20260901T061545Z-69bea0) while inspecting this repo's default head 88b69bb0029c8f5fb63f557a8b8d1a78c16ff63d read-only. No code in this repo was changed by the fleet run. JS, Lint, Rspec, and the demo-fleet smoke are green on that head; this is about the staging deployment only. Review-app repair is already tracked in #784 (repair PR #802), which does not mention the staging app.
Problem
Deploy Staging to Control Plane fails on every master push since PR #777 ("feat(cpflow): add ordered renderer workload", merged 2026-07-13T09:50Z) with the same error:
ERROR: Can't find workload 'node-renderer', please create it with 'cpflow apply-template node-renderer -a react-webpack-rails-tutorial-staging'
Evidence: runs 29240606752, 31473650988, and https://github.com/shakacode/react-webpack-rails-tutorial/actions/runs/33132845651 (push of 88b69bb). The last green staging deploy was 0b2d0b4093 on 2026-07-13T01:17Z (run 29217134396), hours before #777 landed. This is an infrastructure bootstrap gap (the staging app never had the new node-renderer workload template applied), not a code defect.
Proposed fix
Run the one-time bootstrap the error suggests against the staging app, e.g. cpflow apply-template node-renderer -a react-webpack-rails-tutorial-staging (with the staging org token), then re-run the staging deploy workflow and confirm it is green. Consider adding the same apply-template step to .controlplane/readme.md (and to the QA/review-app bootstrap in #784) so future workload additions do not strand existing apps.
Context
Found during React on Rails
17.1.0.rc.1fleet validation (shakacode/react_on_rails#4842, packfleet-20260901T061545Z-69bea0) while inspecting this repo's default head88b69bb0029c8f5fb63f557a8b8d1a78c16ff63dread-only. No code in this repo was changed by the fleet run. JS, Lint, Rspec, and the demo-fleet smoke are green on that head; this is about the staging deployment only. Review-app repair is already tracked in #784 (repair PR #802), which does not mention the staging app.Problem
Deploy Staging to Control Planefails on everymasterpush since PR #777 ("feat(cpflow): add ordered renderer workload", merged 2026-07-13T09:50Z) with the same error:Evidence: runs 29240606752, 31473650988, and https://github.com/shakacode/react-webpack-rails-tutorial/actions/runs/33132845651 (push of
88b69bb). The last green staging deploy was0b2d0b4093on 2026-07-13T01:17Z (run 29217134396), hours before #777 landed. This is an infrastructure bootstrap gap (the staging app never had the newnode-rendererworkload template applied), not a code defect.Proposed fix
Run the one-time bootstrap the error suggests against the staging app, e.g.
cpflow apply-template node-renderer -a react-webpack-rails-tutorial-staging(with the staging org token), then re-run the staging deploy workflow and confirm it is green. Consider adding the sameapply-templatestep to.controlplane/readme.md(and to the QA/review-app bootstrap in #784) so future workload additions do not strand existing apps.