Releases: estuary/flow
Releases · estuary/flow
v0.3.0
Includes new commands:
flowctl raw capture
to run a capture connector in an emulated processflowctl raw suggest-schema
to suggest a new schema for a task that has document schema violations (currently this can only be used by Estuary's internal team but at some point users will also be able to use this)
v0.2.3
v0.2.2
v0.2.1
v0.2.0
draft for pre-release testing of flowctl
dev-sql-flowctl-rc update build WIP
dev-sql
This is the latest development build of the sql branch, which gets updated on every successful build of its branch.
v0.1.8
This release includes a couple of minor fixes to flowctl catalog delete
argument handling.
- The delete subcommand now requires that you provide either
--name
or--prefix
(#909) - The delete
dangerous-auto-approve
argument is now provided as a flag (--dangerous-auto-approve
) as opposed to a positional (true
)
v0.1.7
This release includes a number of fixes and improvements:
- Typescript generation will now fetch collection specs automatically, so you no longer need to have the specs locally for all the source collections of a derivation (#862)
- Fixed a bug in confirmation in catalog publish that caused confirmation message to sometimes not appear.
flowctl draft author
now prunes any extra specs automatically (#865)flowctl draft develop
no longer adds a bunch of extra imports. It now lays everything out in the same way ascatalog pull-specs
- Introduced
flowctl catalog delete
, which works in a single-step (with confirmation), so you no longer need to manually deal with drafts during deletion (#904). flowctl catalog list
was including deleted specs by default. This was updated so that deleted specs are never included unless you explicitly ask for them by providing the new --deleted flag.
v0.1.6
What's changed?
- Added high-level
catalog test
andcatalog publish
subcommands that test or publish a set of specs in a single step. These subcommands wrap up the existingdraft create->author->test|publish->delete
workflow by simply performing all of those steps behind the scenes. - Flow specs are no longer required to
import
each other when referencing Collections defined in another file. You may still useimport
to (only) include other specs whenever the current spec is itself included. - You can now pull live (running) Flow specs into your local directory in a single step, using
flowctl catalog pull-specs
. You can do this by name, prefix, and or by type. - Various other improvements to the CLI to make it more ergonomic