-
Notifications
You must be signed in to change notification settings - Fork 505
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
[filter] refactor apiaggregator #153
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[TASK:easegress-pr-test SUCCESS]megaease/easegress Pull Request 153 Deploy Test Success
Codecov Report
@@ Coverage Diff @@
## main #153 +/- ##
==========================================
+ Coverage 57.81% 57.85% +0.03%
==========================================
Files 38 37 -1
Lines 3658 3656 -2
==========================================
Hits 2115 2115
+ Misses 1437 1435 -2
Partials 106 106
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[TASK:easegress-pr-test FAILED]megaease/easegress Pull Request 153 Deploy Test failed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[TASK:easegress-pr-test FAILED]megaease/easegress Pull Request 153 Deploy Test failed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[TASK:easegress-pr-test SUCCESS]megaease/easegress Pull Request 153 Deploy Test Success
Schrödinger's bot! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[TASK:easegress-pr-test FAILED]megaease/easegress Pull Request 153 Deploy Test failed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[TASK:easegress-pr-test SUCCESS]megaease/easegress Pull Request 153 Deploy Test Success
PartialSucceed bool `yaml:"partialSucceed"` | ||
Timeout string `yaml:"timeout" jsonschema:"omitempty,format=duration"` | ||
MergeResponse bool `yaml:"mergeResponse"` | ||
MaxBodyBytes int64 `yaml:"maxBodyBytes" jsonschema:"omitempty,minimum=0,maximum=102400"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prose add Namespace
in spec with default value default
, in case of another component use this filter to aggregate apis.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we provide this namespace
field, that means I can create a Pipeline with several aggregators to represent different namespace's Pipelines. That's too powerful as just being a filter. (be able to help one pipeline across different namespaces).
So I prefer to keep this filter be used only in the default
namespace currently.
For closing #149
GetHTTPPipeline
intoRawConfigTrafficController
APIAggregator
to useRawConfigTrafficController
for getting pipeline in default namespace.