Meltano schedule --list
Follow-up to #514 (closed)
Problem to solve
(Summarize the problem we are trying to solve in the form of we need to do [A], so that [B] can [C])
Add meltano schedule --list
to see what is scheduled.
Target audience
(For whom are we doing this? Include a persona)
Meltano developer using the CLI
Further details
(Include use cases, benefits, and/or goals)
Proposal
(How are we going to solve the problem? Try to include the user journey)
Add the command.
What does success look like, and how can we measure that?
(Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this)
meltano schedule --list
shows the current ELT schedules in the meltano.yml
Regression test
(Ensure the feature doesn't cause any regressions)
-
Write adequate test cases and submit test results -
Test results should be reviewed by a person from the team
Links / references
Please note that this was taken from GitLab, to be changed accordingly