Open barnabasbusa opened 7 months ago
Hey @barnabasbusa , I'd actually prefer not to do this. Rationale:
kurtosis.yml not found
indicating to the user which they needWhat do you think?
most users (including me) expect that yaml == yml
It took me about 20 mins finding out what it was missing, as I really didn't think that the file format was the issue.
If you see both, yaml and yml then you should throw an error, stating that it's not obvious which one should be used.
Either way issue #1700 specifically asks for not having this file altogether (which would be my preferred way for sure!)
What's your CLI version?
Description & steps to reproduce
There was an error interpreting Starlark code Evaluation error: kurtosis.yml is not found in the path of 'github.com/ethpandaops/dencun-devnets/network-configs/devnet-12'; files can only be accessed from Kurtosis packages. For more information, go to: https://docs.kurtosis.com/advanced-concepts/how-do-kurtosis-imports-work at [github.com/kurtosis-tech/ethereum-package/main.star:103:22]: run at [0:0]: upload_files
Error encountered running Starlark code.
Desired behavior
Would be ideal if
kurtosis.yaml
would also be checked, as sometimes people will use yaml instead of yml.What is the severity of this bug?
Painful; this is causing significant friction in my workflow.
What area of the product does this pertain to?
CLI: the Command Line Interface