Repository navigation
Refuse Node runtimes at validate and in the Render importer (S-002-14, S-002-15) #114
Description
Builds part of spec S-002, docs/specs/002-component-build-steps.md (feature issue #86): the acceptance criteria below. Each needs a test that names its id (test_s002_<k>_..., or a proves: S-002-14 comment line).
- S-002-14:
cloudfall config validateon a Component withruntime.type: node,runtime.type: pm2, orruntime.packageManagerofnpm,pnpmoryarnexitsCONFIG_INVALIDwith codecomponent_runtime_unsupportednaming the field - S-002-15: Importing a Render blueprint with a Node web service writes no Component for it and lists the service as an unsupported gap
Activity
uv sync#86shipmill-romamo commentedon Oct 27, 2026
Triage: implement, for the next release candidate.
The plan: build the criteria listed in the body, as
docs/specs/002-component-build-steps.md(S-002, approved in #98) says, each with a test that names its id. A departure from a criterion goes back as a question, never a quiet change. Build issues start in order: this one starts once every issue on itsDepends onlines has closed. I'll link the PR here.shipmill-romamo commentedon Oct 27, 2026
The build is in #132:
config validaterefuses a Node runtime or a non-uv package manager withcomponent_runtime_unsupported, and the Render importer lists a Node service as an unsupported gap instead of writing a Component. Configs that declare a Node runtime and validate today are refused from this release on, as S-002-14 asks; none in this repo does. This issue closes when #132 merges.Refuse Node runtimes at validate time and in the Render importer
Refuse Node runtimes at validate time and in the Render importer
shipmill-romamo commentedon Oct 27, 2026
Released in v0.8.0rc6 (pre-release). uv tool install --prerelease allow cloudfall==0.8.0rc6
A plain install gets it with the next stable release.
If you filed this: react 👍 on this comment once it works for you, or reply if it doesn't.