You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This command will register the Workspace and create the root config file for you.
62
-
For more information on Workspaces and it's config, see [Workspaces](docs/config/workspace_config.md).
62
+
For more information on Workspaces and it's config, see [Workspaces](docs/types/workspace.md).
63
63
64
64
#### Defining Executables
65
65
66
-
Executables are the core of flow. Each executable is driven by its definition within an executable definition file
67
-
(`*.flow` file). There are several types of executables that can be defined.
68
-
For more information on Executables and it's config, see [Executables](docs/config/executables.md).
66
+
Executables are the core of flow. Each executable is driven by its definition within a flow file (`*.flow`).
67
+
There are several types of executables that can be defined. For more information on Executables and the flow file, see [FlowFile.md](docs/types/flowfile.md).
68
+
69
+
There is also a JSON Schema that can be used in IDEs with the Language Server Protocol (LSP) to perform intelligent
70
+
suggestions. You can add the following comment to the top of your flow files to enable this:
See https://github.com/jahvon/flow/blob/main/docs/config/executables.md#Verbformore information on executable verbs.See https://github.com/jahvon/flow/blob/main/docs/config/executables.md#Reffor more information on executable IDs.
30
+
See https://github.com/jahvon/flow/blob/main/docs/types/flowfile.md#ExecutableVerb for more information on executable verbs.See https://github.com/jahvon/flow/blob/main/docs/types/flowfile.md#ExecutableRef for more information on executable IDs.
Copy file name to clipboardexpand all lines: docs/cli/flow_get_executable.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,8 @@ Print an executable flow by reference.
7
7
Print an executable by the executable's verb and ID.
8
8
The target executable's ID should be in the form of 'ws/ns:name' and the verb should match the target executable's verb or one of its aliases.
9
9
10
-
Seehttps://github.com/jahvon/flow/blob/main/docs/config/executables.md#Verbfor more information on executable verbs.Seehttps://github.com/jahvon/flow/blob/main/docs/config/executable.md#Reffor more information on executable IDs.
10
+
See https://github.com/jahvon/flow/blob/main/docs/types/flowfile.md#ExecutableVerb for more information on executable verbs.
11
+
See https://github.com/jahvon/flow/blob/main/docs/types/flowfile.md#ExecutableRef for more information on executable IDs.
Copy file name to clipboardexpand all lines: docs/types/config.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -27,9 +27,9 @@ Alternatively, a custom path can be set using the `FLOW_CONFIG_PATH` environment
27
27
|`currentWorkspace`| The name of the current workspace. This should match a key in the `workspaces` or `remoteWorkspaces` map. |`string`||[]|
28
28
|`defaultLogMode`| The default log mode to use when running executables. This can either be `hidden`, `json`, `logfmt` or `text``hidden` will not display any logs. `json` will display logs in JSON format. `logfmt` will display logs with a log level, timestamp, and message. `text` will just display the log message. |`string`| logfmt |[]|
|`templates`| A map of flowfile template names to their paths. | map (`string -> string`) | map[]|[]|
30
+
|`templates`| A map of flowfile template names to their paths. |`map` (`string` -> `string`) | map[]|[]|
31
31
|`workspaceMode`| The mode of the workspace. This can be either `fixed` or `dynamic`. In `fixed` mode, the current workspace used at runtime is always the one set in the currentWorkspace config field. In `dynamic` mode, the current workspace used at runtime is determined by the current directory. If the current directory is within a workspace, that workspace is used. |`string`| dynamic |[]|
32
-
|`workspaces`| Map of workspace names to their paths. The path should be a valid absolute path to the workspace directory. | map (`string -> string`) | <novalue> |[]|
32
+
|`workspaces`| Map of workspace names to their paths. The path should be a valid absolute path to the workspace directory. |`map` (`string` -> `string`) | <novalue> |[]|
|`description`| A description of the executables defined within the flow file. This description will be set as the executables' description if not defined at the executable level. |`string`||[]|
|`namespace`| The namespace to be given to all executables in the flow file. If not set, the executables in the file will be grouped into the root (*) namespace. Namespaces can be reused across multiple flow files. Namespaces are used to reference executables in the CLI using the format `workspace:namespace/name`. |`string`||[]|
21
-
|`tags`| Tags to be applied to all executables defined within the flow file. | array (``string``) |[]|[]|
21
+
|`tags`| Tags to be applied to all executables defined within the flow file. |`array` (`string`) |[]|[]|
|`timeout`| The timeout for the request in Go duration format (e.g. 30s, 5m, 1h). |`string`| 30m0s |[]|
285
285
|`transformResponse`| JQ query to transform the response before saving it to a file or outputting it. |`string`||[]|
286
286
|`url`| The URL to make the request to. |`string`||[]|
287
-
|`validStatusCodes`| A list of valid status codes. If the response status code is not in this list, the executable will fail. If not set, the response status code will not be checked. | array (``integer``) |[]|[]|
287
+
|`validStatusCodes`| A list of valid status codes. If the response status code is not in this list, the executable will fail. If not set, the response status code will not be checked. |`array` (`integer`) |[]|[]|
288
288
289
289
### ExecutableRequestResponseFile
290
290
@@ -377,7 +377,7 @@ This allows users to use the verb that best describes the action they are perfor
377
377
378
378
A list of `.sh` files to convert into generated executables in the file's executable group.
0 commit comments