flowctlcommand-line interface is used to test, deploy, and run Flow catalogs. It is the one and only Flow binary that you need to deal with, so distribution and upgrades are all simple. For now, the Docker image is the only official release artifact, but
flowctlwill also be released as a statically linked binary in the near future.
flowctlincludes a number of sub-commands. The most common sub-commands you'll use are
test. We'll talk a bit about each of these in order, as each one builds on the previous.
discoverauto-creates a catalog spec given an open-source connector and a data source. It’s an assisted way to quickly capture data and expedite the initial Flow deployment.
developstarts a small local Flow runtime and applies your catalog spec to it. In essence, you are using Flow as it would be used in production, but with locally running captures and materializations.
applypersists your catalog to a previously set-up Flow deployment for production updates. You pass the address of the etcd cluster and the Flow reactor in your deployment as arguments.
testis used to run your catalog tests and ensure that their output matches your expectations given an input. To do so, it starts the same way as
develop, and then runs each of your tests against that environment.