-
Notifications
You must be signed in to change notification settings - Fork 339
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
chore(ci) split e2e deployment options #2950
Conversation
It's hard to understand which deployment options only apply to the Kuma control plane, and which apply to arbitrarry applications. Split the options in two, and fix up all the relevant option types so that we have strong typing all the way down, and it's obvious which options apply to which tasks. Signed-off-by: James Peach <james.peach@konghq.com>
Codecov Report
@@ Coverage Diff @@
## master #2950 +/- ##
=======================================
Coverage 52.31% 52.31%
=======================================
Files 909 909
Lines 52399 52431 +32
=======================================
+ Hits 27413 27430 +17
- Misses 22792 22806 +14
- Partials 2194 2195 +1
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.
strong typing
👍
LGTM
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.
lgtm
It's hard to understand which deployment options only apply to the Kuma control plane, and which apply to arbitrarry applications. Split the options in two, and fix up all the relevant option types so that we have strong typing all the way down, and it's obvious which options apply to which tasks. Signed-off-by: James Peach <james.peach@konghq.com> (cherry picked from commit 96217b5) # Conflicts: # test/e2e/auth/auth_universal.go
It's hard to understand which deployment options only apply to the Kuma control plane, and which apply to arbitrarry applications. Split the options in two, and fix up all the relevant option types so that we have strong typing all the way down, and it's obvious which options apply to which tasks. Signed-off-by: James Peach <james.peach@konghq.com> (cherry picked from commit 96217b5)
It's hard to understand which deployment options only apply to the Kuma control plane, and which apply to arbitrarry applications. Split the options in two, and fix up all the relevant option types so that we have strong typing all the way down, and it's obvious which options apply to which tasks. Signed-off-by: James Peach <james.peach@konghq.com> (cherry picked from commit 96217b5) Co-authored-by: James Peach <james.peach@konghq.com>
Summary
It's hard to understand which deployment options only apply to the Kuma
control plane, and which apply to arbitrarry applications. Split the
options in two, and fix up all the relevant option types so that we have
strong typing all the way down, and it's obvious which options apply to
which tasks.
Full changelog
N/A
Issues resolved
N/A
Documentation
N/A
Testing
Backwards compatibility
backport-to-stable
label if the code is backwards compatible. Otherwise, list breaking changes.