Open
Description
Describe the bug
When running recipes inside a directory, meteor error messages are not helpful. Even though there is a recipe present, because of recipe errors, meteor returns back no recipes in folder.
To Reproduce
Steps to reproduce the behavior:
- create sample recipe which has some issue
- run the meteor command at directory level
- See error
Expected behavior
running meteor at directory should return all errors for each individual recipe in folder
Screenshots
/tmp # l
total 4
-rw-r--r-- 1 root root 706 Oct 19 07:31 sample-bigquery-recipe.yaml
/tmp # meteor lint /tmp
2022/10/19 07:47:01 unable to find config file, loading from env and defaults: open ./meteor.yaml: no such file or directory
No recipe found in [/tmp]
Use 'meteor gen recipe' to generate a new recipe.
/tmp # meteor run /tmp
2022/10/19 07:47:14 unable to find config file, loading from env and defaults: open ./meteor.yaml: no such file or directory
2022/10/19 07:47:14 unable to find config file, loading from env and defaults: open ./meteor.yaml: no such file or directory
! No recipe found in [/tmp]
/tmp # meteor lint /tmp/sample-bigquery-recipe.yaml
2022/10/19 07:47:29 unable to find config file, loading from env and defaults: open ./meteor.yaml: no such file or directory
Usage: meteor lint [path] [flags]
yaml: line 12: could not find expected ':'
/tmp # meteor run /tmp/sample-bigquery-recipe.yaml
2022/10/19 07:47:35 unable to find config file, loading from env and defaults: open ./meteor.yaml: no such file or directory
2022/10/19 07:47:35 unable to find config file, loading from env and defaults: open ./meteor.yaml: no such file or directory
Usage: meteor run <path>|<name> [flags]
Flags:
-c, --config string file path for agent level config (default "./meteor.yaml")
--var string Path to Config file with env variables for recipe
yaml: line 12: could not find expected ':'
Additional context:
Version: 0.3.1
Metadata
Metadata
Assignees
Labels
No labels