Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

bug: `meltano state list` with pattern - no such option

See original GitHub issue

Meltano Version

2.3.0

Python Version

3.8

Bug scope

CLI (options, error messages, logging, etc.)

Operating System

Mac

Description

It looks like the --pattern argument thats in the docs https://docs.meltano.com/reference/command-line-interface#list isnt available on the CLI.

(meltano) Patricks-MBP:data pnadolny$ meltano --version
meltano, version 2.3.0

(meltano) Patricks-MBP:data pnadolny$ meltano state list --pattern '*tap-gitlab*'
2022-07-25T21:31:25.438941Z [info     ] Environment 'userdev' is active
Usage: meltano state list [OPTIONS] [PATTERN]
Try 'meltano state list --help' for help.

Error: No such option: --pattern

Code

No response

Issue Analytics

State:
Created a year ago
Comments:7 (1 by maintainers)

Top GitHub Comments

2reactions

aaronsteerscommented, Aug 11, 2022

@aaronsteers @tayloramurphy this ended up being really really simple - pattern matching was implemented with push-down to the database, but the CLI pattern was defined as an argument and not an option (as documented). It was a 1-line fix.

However this only gives us what is documented (i.e. use of *), rather than the more expressive options available in select. Given that the implementation of wildcards was done already, and that the select features are not readily reusable, I think it best to go with the minimum " I just want it to match what’s in the docs" unless you feel strongly that more expressive pattern matching is needed at this stage 🙂

@kgpayne - Good call. And thanks for the quick turnaround.

As we discussed offline, there are advantages to keeping a simple * wildcard for now: specifically that this is more likely to be supported as a passthrough glob by state backends during their native list operations.

1reaction

kgpaynecommented, Aug 11, 2022

@aaronsteers @tayloramurphy this ended up being really really simple - pattern matching was implemented with push-down to the database, but the CLI pattern was defined as an argument and not an option (as documented). It was a 1-line fix.

However this only gives us what is documented (i.e. use of *), rather than the more expressive options available in select. Given that the implementation of wildcards was done already, and that the select features are not readily reusable, I think it best to go with the minimum " I just want it to match what’s in the docs" unless you feel strongly that more expressive pattern matching is needed at this stage 🙂

Top Results From Across the Web

Command Line - Meltano Documentation

Meltano provides a command line interface (CLI) that makes it easy to manage your project, plugins, and EL(T) pipelines.To quickly find the meltano...

Complete Tutorial - Meltano Documentation

Create and navigate to a directory to hold your Meltano projects: ... there is no way to include it back without removing the...

Projects - Meltano Documentation

Since a Meltano project is just a directory on your filesystem containing text-based files, you can treat it like any other software development...

Replicate Data

You can use meltano config <plugin> list to list all available settings with their names, environment variables, and current values. meltano config <plugin> ......

State Backends

The state backend settings for your Meltano project can be configured much the same as any other Meltano setting. The main setting is...