Create or update a flow from a JSON file
Synopsis
Creates a flow, or updates it if a flow with that id exists.
The file is either a flow as printed by 'nova flow get', or a bare tree ({"version": ..., "root": ...}) together with --id.
An existing flow is only updated when the file carries the revision the flow still has on the instance (as written by 'nova flow get'). Use --force to replace it regardless. The file keeps its revision after a push: run 'nova flow get' again before pushing further changes.
With --validate, the instance checks the tree first (schema, available actions, globals) and nothing is saved if it is not valid.
nova flow push <file> [flags]
Examples
# save a flow edited after 'nova flow get', only if nobody changed it on the instance meanwhile
nova flow push pick-and-place.json
# check it on the instance first (actions available, globals exist, ...), save only if valid
nova flow push pick-and-place.json --validate
# create a flow from a bare tree ({"version": ..., "root": ...})
nova flow push tree.json --id pick-and-place --name "Pick and place"
# replace the flow on the instance no matter what changed there
nova flow push pick-and-place.json --force
# copy a flow to another id (--force replaces an existing copy)
nova flow push pick-and-place.json --id pick-and-place-copy --force
Options
--force Replace the flow even if it changed on the instance
-h, --help help for push
--id string Flow id (default: the id in the file)
--name string Flow name (default: the name in the file, or the id)
--validate Validate the tree on the instance first and only save it if it is valid
Options inherited from parent commands
--debug Write diagnostic output to stderr: HTTP requests and responses, external commands, the resolved instance. Known secrets are redacted, but bodies (app environments, kubeconfigs) can still contain some: don't share the output unreviewed (env: NOVA_DEBUG=1)
--env string (Wandelbots internal) Portal environment for this invocation: prod, stg or dev (default: the environment of the cloud instance, else of the last 'nova login'; env: NOVA_ENV)
--insecure-skip-tls-verify If true, the server's certificate will not be checked for validity (disables TLS verification for all requests)
--instance string Name of the instance to work against for this invocation (overrides the selected instance; env: NOVA_INSTANCE)
-y, --yes Answer yes to questions, e.g. to install NovaFlow when it is missing
SEE ALSO
- nova flow - Manage NovaFlow and its flows on the current cell