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

[feature]: Add an option to pass the config file #151

Open
2 tasks done
yu-iskw opened this issue Jun 17, 2024 · 0 comments
Open
2 tasks done

[feature]: Add an option to pass the config file #151

yu-iskw opened this issue Jun 17, 2024 · 0 comments

Comments

@yu-iskw
Copy link
Contributor

yu-iskw commented Jun 17, 2024

Check your idea has not already been reported

Edit the title above

  • 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.

bigfun deploy --config path/to/config.yaml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant