[X] I wrote clear short description of my idea in the title above
Tell us everything
Overview
The bigfun command doesn't offer any option to specify the path to a config file. It can read only the default path. If we add an option to pass it, we can more easily switch the deployment destination. For instance, we have the environments for the development and the production. We want to share the deployed functions in both by switching the config file.
Check your idea has not already been reported
Edit the title above
Tell us everything
Overview
The
bigfuncommand doesn't offer any option to specify the path to a config file. It can read only the default path. If we add an option to pass it, we can more easily switch the deployment destination. For instance, we have the environments for the development and the production. We want to share the deployed functions in both by switching the config file.