@uipath/flow-tool 1.0.1 → 1.0.4

package/README.md

@@ -9,7 +9,7 @@ CLI tool for managing UiPath Flow processes and jobs. This is a uip plugin that
 Create a new Flow project with boilerplate files.
 
 ```bash
-uip flow init <projectName> [--force]
+uip maestro flow init <projectName> [--force]
 ```
 
 ### `flow validate`
@@ -17,7 +17,7 @@ uip flow init <projectName> [--force]
 Validate a `.flow` file against the Flow schema (Zod-based) with structural cross-field checks.
 
 ```bash
-uip flow validate <flowFile>
+uip maestro flow validate <flowFile>
 ```
 
 ### `flow pack`
@@ -25,7 +25,7 @@ uip flow validate <flowFile>
 Pack a Flow project into a NuGet package (`.nupkg`).
 
 ```bash
-uip flow pack <projectPath> <outputPath> [-n <name>] [-v <version>]
+uip maestro flow pack <projectPath> <outputPath> [-n <name>] [-v <version>]
 ```
 
 ### Known Issues
@@ -36,7 +36,7 @@ uip flow pack <projectPath> <outputPath> [-n <name>] [-v <version>]
 >
 > **Root cause:** The published `@uipath/tool-flow` npm package has a non-recursive `copyFiles()` method that only copies top-level files from the project directory, silently skipping the `content/` and `flow_files/` subdirectories. The local `flow-pack-service.ts` correctly uses `copyDirectory()` for recursive copies, but the npm-published tool does not.
 >
-> **Workaround:** Use `uip flow pack` directly to produce a correct `.nupkg` for deployment.
+> **Workaround:** Use `uip maestro flow pack` directly to produce a correct `.nupkg` for deployment.
 
 ### Flow Process Commands
 
@@ -45,7 +45,7 @@ uip flow pack <projectPath> <outputPath> [-n <name>] [-v <version>]
 List available Flow processes.
 
 ```bash
-uip flow process list
+uip maestro flow process list
 ```
 
 #### `flow process get`
@@ -53,10 +53,10 @@ uip flow process list
 Get Flow process schema and details.
 
 ```bash
-uip flow process get "<process-key>" "<feed-id>"
+uip maestro flow process get "<process-key>" "<feed-id>"
 
 # Example
-uip flow process get "MyFlow.flow.Flow:1.0.0" "6d98ceb8-becb-46ec-80d7-df213fbec06c"
+uip maestro flow process get "MyFlow.flow.Flow:1.0.0" "6d98ceb8-becb-46ec-80d7-df213fbec06c"
 ```
 
 #### `flow process run`
@@ -66,7 +66,7 @@ Run a Flow process.
 **Syntax:**
 
 ```bash
-uip flow process run "<process-key>" "<folder-key>" [options]
+uip maestro flow process run "<process-key>" "<folder-key>" [options]
 ```
 
 **Arguments:**
@@ -88,20 +88,20 @@ uip flow process run "<process-key>" "<folder-key>" [options]
 
 ```bash
 # Run with JSON inputs
-uip flow process run "TestFlow.flow.Flow:1.0.0" "folder-guid-here" \
+uip maestro flow process run "TestFlow.flow.Flow:1.0.0" "folder-guid-here" \
   --release-key "release-guid" \
   --folder-id "2553016" \
   --inputs '{"name": "John", "age": 30}'
 
 # Run with inputs from file
-uip flow process run "TestFlow.flow.Flow:1.0.0" "folder-guid-here" \
+uip maestro flow process run "TestFlow.flow.Flow:1.0.0" "folder-guid-here" \
   --release-key "release-guid" \
   --folder-id "2553016" \
   --inputs @inputs.json
 
 # Run with piped inputs
 echo '{"name": "John", "age": 30}' | \
-  uip flow process run "TestFlow.flow.Flow:1.0.0" "folder-guid-here" \
+  uip maestro flow process run "TestFlow.flow.Flow:1.0.0" "folder-guid-here" \
   --release-key "release-guid" \
   --folder-id "2553016"
 ```
@@ -113,14 +113,14 @@ echo '{"name": "John", "age": 30}' | \
 Stream execution traces for a running job.
 
 ```bash
-uip flow job traces "<job-key>" [options]
+uip maestro flow job traces "<job-key>" [options]
 
 # Options:
 # --poll-interval <ms>  - Polling interval in milliseconds (default: 2000)
 # --traces-service <name> - Traces service name (default: llmopstenant_)
 
 # Example
-uip flow job traces "06478292-f9cf-4234-9d1b-03f4bcd95fed"
+uip maestro flow job traces "06478292-f9cf-4234-9d1b-03f4bcd95fed"
 ```
 
 #### `flow job status`
@@ -128,35 +128,35 @@ uip flow job traces "06478292-f9cf-4234-9d1b-03f4bcd95fed"
 Get detailed status of a Flow job.
 
 ```bash
-uip flow job status "<job-key>" --folder-id "<id>" [options]
+uip maestro flow job status "<job-key>" --folder-id "<id>" [options]
 
 # Options:
 # --detailed  - Show full response with all fields
 
 # Example
-uip flow job status "06478292-f9cf-4234-9d1b-03f4bcd95fed" --folder-id "2553016"
+uip maestro flow job status "06478292-f9cf-4234-9d1b-03f4bcd95fed" --folder-id "2553016"
 ```
 
 ## Complete Workflow
 
 ```bash
 # 1. List available processes
-uip flow process list
+uip maestro flow process list
 
 # 2. Get process schema (to see required inputs)
-uip flow process get "MyFlow.flow.Flow:1.0.0" "feed-id-from-list"
+uip maestro flow process get "MyFlow.flow.Flow:1.0.0" "feed-id-from-list"
 
 # 3. Run the process
-JOB_KEY=$(uip flow process run "MyFlow.flow.Flow:1.0.0" "folder-key" \
+JOB_KEY=$(uip maestro flow process run "MyFlow.flow.Flow:1.0.0" "folder-key" \
   --release-key "release-key" \
   --folder-id "2553016" \
   --inputs '{}' 2>/dev/null)
 
 # 4. Watch execution traces
-uip flow job traces "$JOB_KEY"
+uip maestro flow job traces "$JOB_KEY"
 
 # 5. Check final status
-uip flow job status "$JOB_KEY" --folder-id "2553016"
+uip maestro flow job status "$JOB_KEY" --folder-id "2553016"
 ```
 
 ## Output
@@ -190,8 +190,8 @@ uip flow job status "$JOB_KEY" --folder-id "2553016"
 Fetches the node registry and writes it to local cache. Subsequent commands (`list`, `search`, `get`) read from this cache.
 
 ```bash
-uip flow registry pull
-uip flow registry pull --force   # bypass 30-minute cache, always refresh
+uip maestro flow registry pull
+uip maestro flow registry pull --force   # bypass 30-minute cache, always refresh
 ```
 
 **Output fields:**
@@ -218,7 +218,7 @@ uip flow registry pull --force   # bypass 30-minute cache, always refresh
 Lists all nodes in the local cache. If no cache exists, fetches live data first.
 
 ```bash
-uip flow registry list
+uip maestro flow registry list
 ```
 
 **Output fields:** `NodesCount`, `Nodes[]`
@@ -230,9 +230,9 @@ uip flow registry list
 Searches for nodes by keyword and/or structured filters.
 
 ```bash
-uip flow registry search slack
-uip flow registry search slack --filter "displayname:contains=send message"
-uip flow registry search --filter "category=connector"
+uip maestro flow registry search slack
+uip maestro flow registry search slack --filter "displayname:contains=send message"
+uip maestro flow registry search --filter "category=connector"
 ```
 
 **Options:**
@@ -284,8 +284,8 @@ Examples:
 Returns full details for a single node, looked up by `nodeType` (case-insensitive).
 
 ```bash
-uip flow registry get "uipath.agent"
-uip flow registry get "uipath.connector.slack.send-message"
+uip maestro flow registry get "uipath.agent"
+uip maestro flow registry get "uipath.connector.slack.send-message"
 ```
 
 **Output fields:** `Node` (enriched FlowNode object)
@@ -320,24 +320,24 @@ All commands support `--output-filter <expression>` (global option) to extract s
 
 ```bash
 # List all nodeTypes from a search
-uip flow registry search slack --output-filter "Nodes[*].nodeType"
+uip maestro flow registry search slack --output-filter "Nodes[*].nodeType"
 
 # Get the full enriched node
-uip flow registry get "uipath.connector.slack.send-message" \
+uip maestro flow registry get "uipath.connector.slack.send-message" \
   --output-filter "Node"
 
 # Extract only the input fields
-uip flow registry get "uipath.connector.slack.send-message" \
+uip maestro flow registry get "uipath.connector.slack.send-message" \
   --output-filter "Node.inputDefinition.fields"
 
 # Get the node count after a pull
-uip flow registry pull --output-filter "NodesCount"
+uip maestro flow registry pull --output-filter "NodesCount"
 ```
 
 Combine with `--output json` to get clean JSON output:
 
 ```bash
-uip flow registry get "uipath.connector.slack.send-message" \
+uip maestro flow registry get "uipath.connector.slack.send-message" \
   --output-filter "Node.inputDefinition.fields" --output json
 ```
 
@@ -347,20 +347,20 @@ uip flow registry get "uipath.connector.slack.send-message" \
 
 ```bash
 # 1. Pull the registry (once per session)
-uip flow registry pull
+uip maestro flow registry pull
 
 # 2. Search for candidates
-uip flow registry search slack --filter "displayname:contains=send" \
+uip maestro flow registry search slack --filter "displayname:contains=send" \
   --output-filter "Nodes[*].nodeType"
 # → uipath.connector.slack.send-message
 #   uipath.agent.resource.tool.connector.slack.send-message
 # Pick the uipath.connector.* variant for direct flow use.
 
 # 3. Inspect the full schema (with IS enrichment if logged in)
-uip flow registry get "uipath.connector.slack.send-message" --output json
+uip maestro flow registry get "uipath.connector.slack.send-message" --output json
 
 # 4. Extract just the input fields to build a request body
-uip flow registry get "uipath.connector.slack.send-message" \
+uip maestro flow registry get "uipath.connector.slack.send-message" \
   --output-filter "Node.inputDefinition.fields" --output json
 ```
 

package/dist/index.js

@@ -1005,7 +1005,7 @@ Expecting one of '${allowedValues.join("', '")}'`);
         this._exitCallback = (err) => {
           if (err.code !== "commander.executeSubCommandAsync") {
             throw err;
-          } else {}
+          }
         };
       }
       return this;