-
Notifications
You must be signed in to change notification settings - Fork 327
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
feat(kuma-cp) friendly response in K8s mode #712
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
subnetmarco
suggested changes
May 1, 2020
nickolaev
force-pushed
the
feat/kumactl_apply_k8s
branch
from
May 1, 2020 16:50
3ad8894
to
3623087
Compare
jakubdyszkiewicz
requested changes
May 4, 2020
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.
Can you add tests (assertions to the body msg) in read_only_resource_endpoints_test.go
?
nickolaev
force-pushed
the
feat/kumactl_apply_k8s
branch
from
May 4, 2020 11:07
3623087
to
ddbcefb
Compare
nickolaev
force-pushed
the
feat/kumactl_apply_k8s
branch
2 times, most recently
from
May 4, 2020 11:26
aac0b71
to
225a075
Compare
jakubdyszkiewicz
approved these changes
May 4, 2020
When kuma-cp is run in Kubernetes mode, all the changes should happen through `kubectl`. Send an explanation in the response body, so clients (i.e. `kumactl`) can show it to the user. Fixes #165 Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
When kuma-cp sends back 405 on resource Create/Update/Delete, just show the message in the body. This makes the message more user friendly. Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
nickolaev
force-pushed
the
feat/kumactl_apply_k8s
branch
from
May 4, 2020 17:28
225a075
to
20b3c31
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When kuma-cp is run in Kubernetes mode, all the changes should happen through
kubectl
. Send an explanation in the response body, so clients (i.e.kumactl
or the HTTP API) can show it to the user.Full changelog
Issues resolved
Fix #165