v0.4.0

This version introduces:

• The latch ls subcommand ~ list the contents of LatchData root or any directory.
• Login and authentication now uses a persistent token. latch login will only need to be run once.

Note that latch login will need to be run again manually after downloading this version.

The latch ls subcommand

Introducing the latch ls subcommand. Use it to "list" the contents of any directory on the platform.

Usage: latch ls [OPTIONS] [REMOTE_DIRECTORIES]...

  List remote files in the command line. Supports multiple directory
  arguments.

  Visit docs.latch.bio to learn more.

Using the subcommand with no arguments will list the contents of your managed root directory.

$ latch ls
Name:                                                           Type:                      Size:         Last Modified:
20A_retests                                                  directory                  -             -
Amplification Project                                    directory                  -             -
Prime_Editing                                               directory                  -             -

Directories can be specified as:

• absolute paths ~ /my/directory
• latch protocol URLs ~ latch:///my/directory
• names within the root of the filesystem ~ my-directory

Persistent Token

The CLI now uses a persistent token with no expiration to authenticate users. This means that users only have to login once. This also means that users of a machine without access to a browser can manually copy their token to ~/.latch/token

The token is still stored at ~/.latch/token and can be found https://console.latch.bio/settings/developer. It is critical that the user engage in best practices when storing this value, eg. avoiding commiting it in VCS or sending it to others via email, slack.

v0.1.0

Dropping two new subcommands:

latch get-wf

Usage: latch get-wf [OPTIONS]

  List workflows.

  Visit docs.latch.bio to learn more.

Options:
  --name TEXT  The name of the workflow to list. Will display all versions
  --help       Show this message and exit.

Usage

Fetch all workflows with the latest version.

$ latch get-wf

59729   wf.batch_ge                     0.0.31
59696   wf-core-batch_ge.wf.batch_ge    0.0.3
59748   wf.guide_counter_wf             0.0.7

Fetch all workflow versions by name.

ID      Name            Version
59698   wf.batch_ge     0.0.13
59703   wf.batch_ge     0.0.18
59704   wf.batch_ge     0.0.19
59715   wf.batch_ge     0.0.22
59716   wf.batch_ge     0.0.23
59723   wf.batch_ge     0.0.25
59724   wf.batch_ge     0.0.26

latch execute

Usage: latch execute [OPTIONS] PARAMS_FILE

  Execute a workflow using a python parameter map.

  Visit docs.latch.bio to learn more.

Options:
  --version TEXT  The version of the workflow to execute. Defaults to latest.
  --help          Show this message and exit.

Usage

$ latch execute foo.py

where foo.py is a python representation of a type map.

# foo.py

from latch.types import LatchFile

params = {
    "_name": "wf.assemble_and_sort",
    "read1": LatchFile("latch:///read1"),
    "read2": LatchFile("latch:///read2"),
}

v0.0.38

• Fixed breaking changes to use of Annotated FlyteFile and FlyteDirectory for python versions <3.9.
• FlyteFile and FlyteDirectory can ingest just a remote path.

v0.0.37

• The LatchDir type allows the use of data with both a local path and remote path. The latter is designated by a latch:/// network scheme and allows reference to arbitrary remote objects within the LatchData managed object store.
• The latch init subcommand now fetches sequencing data to be included in each task’s Docker container in the boilerplate workflow.
• A bug related to building task containers on certain versions of macOS was resolved.

v0.0.30

• LatchFile supports new latch URL scheme
• New multi-task assembly + sorting boilerplate
• latch cp works with new latch URL scheme
• general bug fixes to core subcommand flows