Skip to main content

Add a node straight from a workflow to a catalog

POST 
/api/add_catalog_node

Copies a node out of a workflow into a catalog published from here.

The same destination as add_catalog_node_template, reached without the detour through a project template. Making a template first is the right move when the shape is worth keeping in the project; when it is not, it means maintaining a second copy of the adapter that exists only to be promoted, and every code change has to be pushed through it in order.

What is copied is the node as it stands in the author's own clone, minus three things it must not ship:

  • the files its pinned libraries put there. Linking a library hard- copies it into the node, so those files are sitting among the node's own. They belong to the pin, which a subscriber resolves from the catalog's own copy of that version - carrying them as well would freeze a library's code into the template and leave it there after the pin moved on.
  • its samples, unless asked for. A sample is a message someone captured to test against, so on a live grid it is real traffic.
  • its secrets. Blanked, not refused, and reported back.

What the node pins travels with it: any published library version the catalog does not already ship is copied in alongside, in the same commit. An adapter and the versions it names are one shippable unit - a catalog holding the node alone is a node no subscriber can build. A version the project never published cannot come, and is reported instead: a catalog ships immutable snapshots, and a working copy is a draft.

A name the catalog already has is how a new version of an adapter is released, so it is supported - but only with overwrite, since it discards what subscribers currently pull. Their existing nodes are unaffected either way: create_node copies a template's files into the node, so nothing is reaching back into a running workflow.

Nothing is published by this - the catalog is committed locally, and Publish is what sends it to the repository.

Request​

Responses​

Successful Response