Closed johnsmyth closed 7 months ago
~change --pipeline-arg to --arg~
--pipeline-arg
--arg
~change flowpipe run to be "serverless" by deafult~ ~- use --host o connect to a server instance instead~
flowpipe run
--host
~remove flowpipe service commands, implemement flowpipe server~
flowpipe service
flowpipe server
--port
--listen
!rename --api-host to --host. ~
--api-host
http://localhost:7103
~remove --api-port~
--api-port
~change --execution mode synchronous to --detach (flag/boolean)~
--execution mode synchronous
--detach
~Add tags, documentation for all top-level resource (pipelines, triggers, integrations)~
tags
documentation
pipelines
triggers
integrations
~--output doesnt work - should work for ALL commands~
--output
~Add --watch=false arg to flowpipe server~
--watch=false
~flowpipe trigger show should show all the trigger urls~
flowpipe trigger show
~Do we need a --progress flag???~
--progress
~implement FLOWPIPE_MEMORY_MAX / memory_max_mb~
FLOWPIPE_MEMORY_MAX
memory_max_mb
Allow short form of ids
query step - dbs other than postgres
sql
sql/driver
query step - passing args (how does this work?)
~query trigger~
sqlite event store
~opengraph stuff for flowpipe mod (should work like steampipe)~
mod
~base = in workspaces?~
base =
allow multiple methods on http trigger
~implement workspaces~
~reconcile all CLI args / environment variables / workspace options~
~container - build from source~
source
do we support sensitive on variables, params, or outputs? how are they handled?
sensitive
redact secrets in CLI display
--reveal
--output reveal
change the flowpipe metadata from htpp trigger to be returned in the header instead of the body
execution mode on triggers? "custom" response body / header from triggers?
container "combined" stdout / stderr
container
review flag for mod install on private repo - do we need a flag at all? can we just attempt both?
implement telemetry FLOWPIPE_TELEMETRY
FLOWPIPE_TELEMETRY
implement update check - FLOWPIPE_UPDATE_CHECK
FLOWPIPE_UPDATE_CHECK
implement settable log levels: FLOWPIPE_LOG_LEVEL
FLOWPIPE_LOG_LEVEL
Mod update with branches
remove --install-dir
--install-dir
flowpipe completion
pipes integration: flowpipe login, PIPES_TOKEN, PIPES_HOST, FLOWPIPE_CLOUD_HOST, FLOWPIPE_CLOUD_TOKEN etc
flowpipe login
base = on triggers?
FLOWPIPE_MAX_PARALLEL
FLOWPIPE_QUERY_TIMEOUT
FLOWPIPE_CACHE_TTL
FLOWPIPE_CACHE
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.
Moved to Flowpipe Wiki
Tasks
~change
--pipeline-arg
to--arg
~~change
flowpipe run
to be "serverless" by deafult~ ~- use--host
o connect to a server instance instead~~remove
flowpipe service
commands, implemementflowpipe server
~--port
toflowpipe server
. This is only the port to LISTEN on, not to connect to (which is in the host)~--listen
toflowpipe server
~!rename
--api-host
to--host
. ~http://localhost:7103
~~remove
--api-port
~~change
--execution mode synchronous
to--detach
(flag/boolean)~~Add
tags
,documentation
for all top-level resource (pipelines
,triggers
,integrations
)~~
--output
doesnt work - should work for ALL commands~~Add
--watch=false
arg toflowpipe server
~~
flowpipe trigger show
should show all the trigger urls~~Do we need a
--progress
flag???~~implement
FLOWPIPE_MEMORY_MAX
/memory_max_mb
~Allow short form of ids
query step - dbs other than postgres
sql
andsql/driver
packagesquery step - passing args (how does this work?)
~query trigger~
sqlite event store
~opengraph stuff for flowpipe
mod
(should work like steampipe)~~
base =
in workspaces?~allow multiple methods on http trigger
~implement workspaces~
~reconcile all CLI args / environment variables / workspace options~
~container - build from
source
~Needs design & prioritization
do we support
sensitive
on variables, params, or outputs? how are they handled?redact secrets in CLI display
--reveal
flag?--output reveal
?)change the flowpipe metadata from htpp trigger to be returned in the header instead of the body
execution mode on triggers? "custom" response body / header from triggers?
container
"combined" stdout / stderrreview flag for mod install on private repo - do we need a flag at all? can we just attempt both?
implement telemetry
FLOWPIPE_TELEMETRY
implement update check -
FLOWPIPE_UPDATE_CHECK
implement settable log levels:
FLOWPIPE_LOG_LEVEL
Mod update with branches
remove
--install-dir
Out of scope - open issues for these?
flowpipe completion
pipes integration:
flowpipe login
, PIPES_TOKEN, PIPES_HOST, FLOWPIPE_CLOUD_HOST, FLOWPIPE_CLOUD_TOKEN etcbase =
on triggers?Out of scope - Needs design
FLOWPIPE_MAX_PARALLEL
?FLOWPIPE_QUERY_TIMEOUT
?FLOWPIPE_CACHE_TTL
?FLOWPIPE_CACHE
?