The Environments.create() Protocol in src/posit/connect/environments.py lists explicit keyword arguments for python, r, quarto, and tensorflow installations, but not nodejs.
Connect is adding support for nodejs.installations as an option for execution environments.
POST /v1/environments accepts itPUT /v1/environments/{guid} also accepts it- and
GET always returns it.
At runtime the underlying _ResourceSequence.create(**attributes) happily POSTs a nodejs=... kwarg, so the SDK works against the new field today.
The gap is purely typing: static type-checkers and IDE autocomplete flag nodejs=... as unexpected.
Suggested change
Add nodejs: Installations | None = ... alongside the other language kwargs in three places in src/posit/connect/environments.py:
Environment.updateEnvironments.createEnvironments.find_by
Node.js content support is currently behind EarlyAccess.NodeJs` in Connect, but the field shape mirrors the other languages exactly.
The
Environments.create()Protocol insrc/posit/connect/environments.pylists explicit keyword arguments forpython,r,quarto, andtensorflowinstallations, but notnodejs.Connect is adding support for
nodejs.installationsas an option for execution environments.POST /v1/environmentsaccepts itPUT /v1/environments/{guid}also accepts itGETalways returns it.At runtime the underlying
_ResourceSequence.create(**attributes)happily POSTs anodejs=...kwarg, so the SDK works against the new field today.The gap is purely typing: static type-checkers and IDE autocomplete flag
nodejs=...as unexpected.Suggested change
Add
nodejs: Installations | None = ...alongside the other language kwargs in three places insrc/posit/connect/environments.py:Environment.updateEnvironments.createEnvironments.find_byNode.js content support is currently behindEarlyAccess.NodeJs` in Connect, but the field shape mirrors the other languages exactly.