Getting started ​

Prerequisites

Your administrator should complete Data plane setup before you move to this section.

Typographic conventions

In the examples below, we show commands being invoked within a terminal. When the context of a command is important we show a terminal prompt that looks like this:

shell
[current-directory]: current-python-virtual-environment
$ command
[current-directory]: current-python-virtual-environment
$ command

Your terminal prompt may, of course, look slightly different.

This section walks you through building your first Flyte workflow and deploying it on Union Cloud.

The first part of this tutorial is similar to Getting Started for Flyte, but adapted for Union Cloud.

Learning more about Flyte ​

There is a lot to learn about Flyte and we won't be covering all of it in these docs. The best source for that information is the Flyte open-source project itself:

And here are some pointers to specific sections that you might find helpful:

Differences between Flyte and Union Cloud

As you read the Flyte docs keep in mind a few of the differences between Flyte and Union Cloud:

  • The command-line tool for Flyte OSS is flytectl. The one for Union Cloud is uctl. They are identical except that uctl has a few extra Union Cloud-specific features.
  • The default local configuration location for Flyte is ~/.flyte/ while for Union Cloud it is ~/.uctl/.