-
Notifications
You must be signed in to change notification settings - Fork 492
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
Group configurations by a single Yaml file #29
Comments
I agree this feature can bring huge simplicity for Easegress CLI users. Since we are dealing with manage API framework replacement, I will implement this feature as soon as the replacement completed. |
nevill
referenced
this issue
in nevill/easegress
Sep 2, 2021
nevill
referenced
this issue
in nevill/easegress
Sep 3, 2021
benja-wu
pushed a commit
that referenced
this issue
Sep 7, 2021
* improve egctl to support sending multi configs at once (fix #29) * add a visitor to do the YAML parsing * rollback function readFromFileOrStdin * Update comments. Co-authored-by: Bomin Zhang <[email protected]> * some improvements - change the signature of VisitorFunc - remove useless function readFromFileOrStdin Co-authored-by: Bomin Zhang <[email protected]>
xmh19936688
referenced
this issue
in xmh19936688/easegress
Sep 13, 2021
…egress-io#230) * improve egctl to support sending multi configs at once (fix #29) * add a visitor to do the YAML parsing * rollback function readFromFileOrStdin * Update comments. Co-authored-by: Bomin Zhang <[email protected]> * some improvements - change the signature of VisitorFunc - remove useless function readFromFileOrStdin Co-authored-by: Bomin Zhang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Many applications require multiple configurations to be created, such as an
HttpServer
and aPipelineFilter
. Management of multiple configurations that grouped together in a single file (separated by --- in YAML) will bring huge simplicity to users.like Kubernetes [1]
[1] https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/
The text was updated successfully, but these errors were encountered: