A command-line interface for interacting with Flyte¶
The FlyteCLI is a command-line tool that allows users to perform administrative tasks on their Flyte workflows and executions. It is an independent module but installed as part of the Flyte Kit <components-flytekit>. It primarily iteracts with the FlyteAdmin <components-flyteadmin> service over its gRPC interface, allowing users to list registered workflows, or get a currently running execution.
The easist way to install FlyteCLI is using virtual environments.
Follow the official doc to install the
virtualenv package if
you don’t already have it in your development environment.
Install from source¶
Now that you have virtualenv, you can either install flyte-cli from source.
To do this first clone the git repository and
after setting up and activating your virtual environment, change directory to
the root directory of the flytecli package, and install the dependencies with
pip install -e ..
Install from pypi [recommended]¶
Another option is to just install flyte-cli from prebuilt binaries
Testing if you have a working installation¶
To test whether you have a successful installation of flytecli, run
If you see the following output, you have installed the FlyteCLI successfully.
Usage: flyte-cli [OPTIONS] COMMAND [ARGS]... Command line tool for interacting with all entities on the Flyte Platform. Options: -n, --name TEXT [Optional] The name to pass to the sub-command (if ... Commands: execute-launch-plan Kick off a launch plan. ...
This section introduces and explains the most commonly used terms and concepts the users will see in FlyteCLI.
Host refers to your running Flyte instance and is a common
argument for the commands in FlyteCLI. The FlyteCLI will only be interacting
with the Flyte instance at the URL you specify with the
parameter. This is a required argument for most of the FlyteCLI commands.
Project is a multi-tenancy primitive in Flyte and allows logical grouping
of instances of Flyte entities by users. Within Lyft’s context, this term
usually refers to the name of the Github repository in which your workflow
For more information see Projects
domain refers to development environment (or the service instance)
of your workflow/execution/launch plan/etc. You can specify it with the
domain argument. Values can be either
production. See Domains
name of a named entity is a randomly generated hash assigned
automatically by the system at the creation time of the named entity. For some
commands, this is an optional argument.
Name Entity is a primitive in Flyte that allows logical grouping of
processing entities across versions. The processing entities to which this term
can refer include unversioned
tasks. In other words, an unversioned
entity is essentially a group of multiple workflows that
have the same
Name, but different versions.
URN is a FlyteCLI-only concept. You won’t see this term in other flyte modules.
URN stands for “unique resource name”, and is the identifier of a version of a given named entity, such as a workflow, a launch plan, an execution, or a task. Each URN uniquely identifies a named entity. URNs are often used in FlyteCLI to interact with specific named entities.
The URN of a version of a name entity is composible from the entity’s
attributes. For example, the URN of a workflow can be composed of a prefix
wf and the workflow’s
in the form of
Note that execution is the sole exception here as an execution does not
have versions. The URN of an execution, therefore, is in the form of
FlyteCLI uses subcommands. Whenever you feel unsure about the usage or
the arguments of a command or a subcommand, get help by running
flyte-cli --help or
flyte-cli <subcommand> --help
For information on available commands in FlyteCLI, refer to FlyteCLI’s help message.