Open aaronsteers opened 1 year ago
Just to reaffirm why 4. is necessary: because the VS Code extension otherwise won't work (right now) :-) (And I do want to change the default environment to codespaces, so we do kind of need a meltano.yml in place)
So I do think that's fine, although I also was thinking about a "tutorial" command. Some CLIs have that and it's kind of nice. I think and enables an even better workflow control.
I also was thinking about a "tutorial" command.
Interesting idea! Do you mind logging an issue or discussion for meltano tutorial
as a top level command?
Since we're asking the user to copy-paste one or two commands anyway, I think it would be easier to understand if we try to replace
meltano_tut
references with their native invocations.meltano_tut init
tutorial_reset.sh
.data
ortutorial_data
and just access it from there during the EL step.meltano init .
.