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
Proposal: Default to a 'well-known' named stack file #71
Comments
Good suggestion. We were talking about this recently. I think Are you interested in completing the work also? @johnmccabe - can the |
At this stage i'm not sure if I have the capacity to contribute, though if I find I do down the line and it isn't implemented yet, happy to take a shot at it then. |
@alexellis that should be straight forward, the only bit that is worth calling out is the expected behaviour when passing explicit flags and no Goes without saying I'm a +1 on the idea. |
Can you give an example? |
I would see this as being "stack.yml". We have to make sure that the override works well with all the commands before merging a fix. |
I can take a look at this in the morning |
See #126 |
This has been merged. |
Expected Behaviour
In a similar vein to
docker compose
it would be nice iffaas-cli
defaulted to a well-known, named yaml file (egopenfaas.yml
or similar) If it did, it wouldn't be a requirement to specify-f foo.yaml
on each CLI command.The text was updated successfully, but these errors were encountered: