Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hard-to-understand error message when building from a dir missing porter.yaml #2926

Closed
edespong opened this issue Sep 25, 2023 · 0 comments · Fixed by #2995
Closed

Hard-to-understand error message when building from a dir missing porter.yaml #2926

edespong opened this issue Sep 25, 2023 · 0 comments · Fixed by #2995
Labels
bug Oops, sorry!

Comments

@edespong
Copy link

Describe the bug

When manually creating a porter.yaml and trying to build it, I mistakenly named it porter.yml. Then when running porter build it fails and the error message could be more clear to help indicating the error. Other, commands like porter publish are a lot more helpful when doing something wrong.

To Reproduce

> mkdir unclear-message
> cd unclear-message
> porter create
> mv porter.yaml porter.yml
> porter build

Expected behavior

An output more in line with what porter publish gives:

$ porter publish
could not find porter.yaml in the current directory ~/unclear-message, make sure you are in the right directory or specify the porter manifest with --file

Porter Command and Output

$ porter build
unable to read manifest file : could not read the manifest at "": read ~/unclear-message: is a directory
unable to generate manifest: unable to read manifest file : could not read the manifest at "": read ~/unclear-message: is a directory

Version

porter v1.0.14 (0e739d8)

@edespong edespong added the bug Oops, sorry! label Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Oops, sorry!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant