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
Feature Request: Defaults in serverless.yaml #1487
Comments
Good point. /cc @eahefnawy |
@danhumphrey hmmm we used to do that, but we thought it's best if we follow "convention over configuration". Just keeping the config file as minimal as possible and include only essential data and keep the rest as overwrite-able defaults. but just like @pmuens mentioned, we may put in commented config just for the sake of demonstration. |
@eahefnawy @pmuens convention over configuration is good assuming that the default config works for the majority of users. Is it an accurate assumption that the majority of users will want to use the same region? or am I misunderstanding this? Commented config sounds good, but #1374 is closed. Is this still under consideration. |
@danhumphrey It's closed but we're about to implement this in v1 (in a future release). |
A commented out section in the The |
When creating a new service, I would like to see the defaults in the
serverless.yaml
file. I think this avoids ambiguity. The defaults can be edited or removed, but I think the visibility helps with understanding.If I'm not following protocol in raising this, please correct me..
The text was updated successfully, but these errors were encountered: