You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 9, 2024. It is now read-only.
Following the docs one approach for storage is "just config files, reloaded on file change". This could be very useful if the configuration does not change very often, and should be based on some static file-storage, source-control or configmap. In such case the embedded etcd could be good enough, but it is still not easy to load the static configuration whenever the container starts.
Please add a flag like '-load ' to load an initial configuration from some mounted json/yaml file. This file should describe all the functions and subscriptions that needs to be created.
Other solutions could be:
Using the entire serverless platform and deploying with the serverless cli.
Injecting the configuration whenever the container loads, using a separated container.
Dumping the embedded-etcd to a file and mounting it when the container loads.
All of these solutions seem to me as heavy to lift, especially for a small projects that needs to forward few simple events.
Thanks
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a Feature Proposal
Following the docs one approach for storage is "just config files, reloaded on file change". This could be very useful if the configuration does not change very often, and should be based on some static file-storage, source-control or configmap. In such case the embedded etcd could be good enough, but it is still not easy to load the static configuration whenever the container starts.
Please add a flag like '-load ' to load an initial configuration from some mounted json/yaml file. This file should describe all the functions and subscriptions that needs to be created.
Other solutions could be:
All of these solutions seem to me as heavy to lift, especially for a small projects that needs to forward few simple events.
Thanks
The text was updated successfully, but these errors were encountered: