fix: add back missing verbs

Author: jahvon

cmd/internal/exec.go

@@ -113,7 +113,7 @@ func execFunc(ctx *context.Context, cmd *cobra.Command, verb executable.Verb, ar
 	if err != nil {
 		logger.FatalErr(err)
 	}
-	s, err := store.NewStore()
+	s, err := store.NewStore(store.Path())
 	if err != nil {
 		logger.FatalErr(err)
 	}
@@ -145,7 +145,7 @@ func execFunc(ctx *context.Context, cmd *cobra.Command, verb executable.Verb, ar
 		logger.FatalErr(err)
 	}
 	dur := time.Since(startTime)
-	processStore, err := store.NewStore()
+	processStore, err := store.NewStore(store.Path())
 	if err != nil {
 		logger.Errorf("failed clearing process store\n%v", err)
 	}

cmd/internal/store.go

@@ -70,7 +70,7 @@ func storeSetFunc(ctx *context.Context, _ *cobra.Command, args []string) {
 		value = strings.Join(args[1:], " ")
 	}
 
-	s, err := store.NewStore()
+	s, err := store.NewStore(store.Path())
 	if err != nil {
 		ctx.Logger.FatalErr(err)
 	}
@@ -105,7 +105,7 @@ func registerStoreGetCmd(ctx *context.Context, rootCmd *cobra.Command) {
 func storeGetFunc(ctx *context.Context, _ *cobra.Command, args []string) {
 	key := args[0]
 
-	s, err := store.NewStore()
+	s, err := store.NewStore(store.Path())
 	if err != nil {
 		ctx.Logger.FatalErr(err)
 	}
@@ -148,7 +148,7 @@ func storeClearFunc(ctx *context.Context, cmd *cobra.Command, _ []string) {
 		ctx.Logger.PlainTextSuccess("Store store cleared")
 		return
 	}
-	s, err := store.NewStore()
+	s, err := store.NewStore(store.Path())
 	if err != nil {
 		ctx.Logger.FatalErr(err)
 	}

docs/cli/flow_library.md

@@ -14,7 +14,7 @@ flow library [flags]
   -h, --help               help for library
   -n, --namespace string   Filter executables by namespace.
   -t, --tag stringArray    Filter by tags.
-  -v, --verb string        Filter executables by verb. One of: [abort activate add analyze apply build bundle check clean clear compile create deactivate delete deploy destroy disable enable erase exec execute fetch generate get init inspect install kill launch lint monitor new open package pause publish purge push reboot refresh release reload remove request reset restart retrieve run scan send set setup show start stop teardown terminate test tidy track trigger undeploy uninstall unset validate verify view watch]
+  -v, --verb string        Filter executables by verb. One of: [abort activate add analyze apply build bundle check clean clear compile create deactivate debug delete deploy destroy disable edit enable erase exec execute fetch fix generate get init inspect install kill launch lint modify monitor new open package patch pause profile publish purge push reboot refresh release reload remove request reset restart retrieve run scan send set setup show start stop teardown terminate test tidy trace track transform trigger undeploy uninstall unset update upgrade validate verify view watch]
   -w, --workspace string   Filter executables by workspace.
 ```
 

docs/cli/flow_library_glance.md

@@ -15,7 +15,7 @@ flow library glance [flags]
   -n, --namespace string   Filter executables by namespace.
   -o, --output string      Output format. One of: yaml, json, doc, or list.
   -t, --tag stringArray    Filter by tags.
-  -v, --verb string        Filter executables by verb. One of: [abort activate add analyze apply build bundle check clean clear compile create deactivate delete deploy destroy disable enable erase exec execute fetch generate get init inspect install kill launch lint monitor new open package pause publish purge push reboot refresh release reload remove request reset restart retrieve run scan send set setup show start stop teardown terminate test tidy track trigger undeploy uninstall unset validate verify view watch]
+  -v, --verb string        Filter executables by verb. One of: [abort activate add analyze apply build bundle check clean clear compile create deactivate debug delete deploy destroy disable edit enable erase exec execute fetch fix generate get init inspect install kill launch lint modify monitor new open package patch pause profile publish purge push reboot refresh release reload remove request reset restart retrieve run scan send set setup show start stop teardown terminate test tidy trace track transform trigger undeploy uninstall unset update upgrade validate verify view watch]
   -w, --workspace string   Filter executables by workspace.
 ```
 

docs/guide/conditional.md

@@ -87,9 +87,9 @@ executables:
     serial:
       execs:
         - cmd: flow store set feature-flag enabled
-        - if: data["feature-flag"] == "enabled"
+        - if: store["feature-flag"] == "enabled"
           cmd: echo "Feature is enabled"
-        - if: len(data["optional-key"]) > 0
+        - if: len(store["optional-key"]) > 0
           cmd: echo "Optional key exists"
 ```
 
@@ -105,7 +105,7 @@ executables:
       execs:
         - if: os == "linux" and env["CI"] == "true"
           cmd: echo "Running in Linux CI environment"
-        - if: len(data["build-id"]) > 0 and (os == "darwin" or os == "linux")
+        - if: len(store["build-id"]) > 0 and (os == "darwin" or os == "linux")
           cmd: echo "Valid build on Unix-like system"
 ```
 

docs/schemas/flowfile_schema.json

@@ -510,7 +510,7 @@
       }
     },
     "ExecutableVerb": {
-      "description": "Keywords that describe the action an executable performs. While executables are configured with a single verb, \nthe verb can be aliased to related verbs within its group. For example, the `activate` verb can be replaced \nwith \"enable\" or \"start\" when referencing an executable. This allows users to use the verb that best describes \nthe action they are performing.\n\n### Verb Groups\n\n- **Activation Group**: `activate`, `enable`, `start`, `trigger`\n- **Execution Group**: `exec`, `run`, `execute`\n- **Deactivation Group**: `deactivate`, `disable`, `stop`, `pause`\n- **Termination Group**: `kill`, `terminate`, `abort`\n- **Monitoring Group**: `watch`, `monitor`, `track`\n- **Restart Group**: `restart`, `reboot`, `reload`, `refresh`\n- **Installation Group**: `install`, `setup`, `deploy`\n- **Build Group**: `build`, `package`, `bundle`, `compile`\n- **Uninstallation Group**: `uninstall`, `teardown`, `undeploy`\n- **Update Group**: `update`, `upgrade`, `patch`\n- **Configuration Group**: `configure`, `manage`\n- **Edit Group**: `edit`, `transform`, `modify`\n- **Publish Group**: `publish`, `release`\n- **Distribution Group**: `push`, `send`, `apply`\n- **Test Group**: `test`, `validate`, `check`, `verify`\n- **Analysis Group**: `analyze`, `scan`, `lint`, `inspect`\n- **Launch Group**: `open`, `launch`, `show`, `view`\n- **Creation Group**: `create`, `generate`, `add`, `new`, `init`\n- **Set Group**: `set`\n- **Destruction Group**: `remove`, `delete`, `destroy`, `erase`\n- **Unset Group**: `unset`, `reset`\n- **Cleanup Group**: `clean`, `clear`, `purge`, `tidy`\n- **Retrieval Group**: `retrieve`, `fetch`, `get`, `request`\n\n### Usage Notes\n\n1. [Verb group + Name] must be unique within the namespace of the workspace.\n2. When referencing an executable, users can use any verb from the appropriate group.\n3. Choose the verb that most accurately describes the action being performed.\n4. Be consistent in verb usage within projects or teams to maintain clarity.\n\n### Examples\n\n- An executable configured with the `activate` verb could also be referenced using \"enable\" or \"start\".\n- A build process might use `build` as its primary verb, but could also be invoked with \"package\" or \"assemble\".\n- A cleanup routine configured with `clean` could be called using \"purge\" or \"sanitize\" for more specific connotations.\n  \nBy organizing verbs into these groups, flow provides flexibility in how actions are described while maintaining a \nclear structure for executable operations.\n",
+      "description": "Keywords that describe the action an executable performs. While executables are configured with a single verb, \nthe verb can be aliased to related verbs within its group. For example, the `activate` verb can be replaced \nwith \"enable\" or \"start\" when referencing an executable. This allows users to use the verb that best describes \nthe action they are performing.\n\n### Verb Groups\n\n- **Activation Group**: `activate`, `enable`, `start`, `trigger`\n- **Execution Group**: `exec`, `run`, `execute`\n- **Deactivation Group**: `deactivate`, `disable`, `stop`, `pause`\n- **Termination Group**: `kill`, `terminate`, `abort`\n- **Monitoring Group**: `watch`, `monitor`, `track`\n- **Restart Group**: `restart`, `reboot`, `reload`, `refresh`\n- **Installation Group**: `install`, `setup`, `deploy`\n- **Build Group**: `build`, `package`, `bundle`, `compile`\n- **Uninstallation Group**: `uninstall`, `teardown`, `undeploy`\n- **Update Group**: `update`, `upgrade`, `patch`\n- **Configuration Group**: `configure`, `manage`\n- **Edit Group**: `edit`, `transform`, `modify`, `fix`\n- **Publish Group**: `publish`, `release`\n- **Distribution Group**: `push`, `send`, `apply`\n- **Test Group**: `test`, `validate`, `check`, `verify`\n- **Analysis Group**: `analyze`, `scan`, `lint`, `inspect`\n- **Launch Group**: `open`, `launch`, `show`, `view`\n- **Creation Group**: `create`, `generate`, `add`, `new`, `init`\n- **Set Group**: `set`\n- **Destruction Group**: `remove`, `delete`, `destroy`, `erase`\n- **Unset Group**: `unset`, `reset`\n- **Cleanup Group**: `clean`, `clear`, `purge`, `tidy`\n- **Retrieval Group**: `retrieve`, `fetch`, `get`, `request`\n- **Debug Group**: `debug`, `trace`, `profile`\n\n### Usage Notes\n\n1. [Verb group + Name] must be unique within the namespace of the workspace.\n2. When referencing an executable, users can use any verb from the appropriate group.\n3. Choose the verb that most accurately describes the action being performed.\n4. Be consistent in verb usage within projects or teams to maintain clarity.\n\n### Examples\n\n- An executable configured with the `activate` verb could also be referenced using \"enable\" or \"start\".\n- A build process might use `build` as its primary verb, but could also be invoked with \"package\" or \"assemble\".\n- A cleanup routine configured with `clean` could be called using \"purge\" or \"sanitize\" for more specific connotations.\n  \nBy organizing verbs into these groups, flow provides flexibility in how actions are described while maintaining a \nclear structure for executable operations.\n",
       "type": "string",
       "default": "exec",
       "enum": [
@@ -553,6 +553,7 @@
         "edit",
         "transform",
         "modify",
+        "fix",
         "publish",
         "release",
         "push",
@@ -589,7 +590,10 @@
         "retrieve",
         "fetch",
         "get",
-        "request"
+        "request",
+        "debug",
+        "trace",
+        "profile"
       ]
     },
     "FromFile": {

docs/types/flowfile.md

@@ -388,7 +388,7 @@ the action they are performing.
 - **Uninstallation Group**: `uninstall`, `teardown`, `undeploy`
 - **Update Group**: `update`, `upgrade`, `patch`
 - **Configuration Group**: `configure`, `manage`
-- **Edit Group**: `edit`, `transform`, `modify`
+- **Edit Group**: `edit`, `transform`, `modify`, `fix`
 - **Publish Group**: `publish`, `release`
 - **Distribution Group**: `push`, `send`, `apply`
 - **Test Group**: `test`, `validate`, `check`, `verify`
@@ -400,6 +400,7 @@ the action they are performing.
 - **Unset Group**: `unset`, `reset`
 - **Cleanup Group**: `clean`, `clear`, `purge`, `tidy`
 - **Retrieval Group**: `retrieve`, `fetch`, `get`, `request`
+- **Debug Group**: `debug`, `trace`, `profile`
 
 ### Usage Notes
 
@@ -460,6 +461,7 @@ clear structure for executable operations.
 - `edit`
 - `transform`
 - `modify`
+- `fix`
 - `publish`
 - `release`
 - `push`
@@ -497,6 +499,9 @@ clear structure for executable operations.
 - `fetch`
 - `get`
 - `request`
+- `debug`
+- `trace`
+- `profile`
 
 
 

internal/runner/parallel/parallel.go

@@ -47,7 +47,7 @@ func (r *parallelRunner) Exec(
 	}
 
 	if len(parallelSpec.Execs) > 0 {
-		str, err := store.NewStore()
+		str, err := store.NewStore(store.Path())
 		if err != nil {
 			return err
 		}

internal/runner/serial/serial.go

@@ -47,7 +47,7 @@ func (r *serialRunner) Exec(
 	}
 
 	if len(serialSpec.Execs) > 0 {
-		str, err := store.NewStore()
+		str, err := store.NewStore(store.Path())
 		if err != nil {
 			return err
 		}

internal/services/store/store.go

@@ -40,8 +40,13 @@ type BoltStore struct {
 	processBucket string
 }
 
-func NewStore() (Store, error) {
-	db, err := bolt.Open(Path(), 0666, &bolt.Options{Timeout: 5 * time.Second})
+// NewStore creates a new store with a given db path
+// If dbPath is empty, it will use the default path
+func NewStore(dbPath string) (Store, error) {
+	if dbPath == "" {
+		dbPath = Path()
+	}
+	db, err := bolt.Open(dbPath, 0666, &bolt.Options{Timeout: 5 * time.Second})
 	if err != nil {
 		return nil, fmt.Errorf("failed to open db: %w", err)
 	}