Skip to content

YSH-98: Remove default scope in delete interceptor - #111

Merged
ShannonAmandaAmarasekara merged 6 commits into
mainfrom
YSH-98-remove-default-scope-delete
Jul 4, 2025
Merged

ShannonAmandaAmarasekara merged 6 commits into
mainfrom
YSH-98-remove-default-scope-delete

Conversation

@ShannonAmandaAmarasekara

@ShannonAmandaAmarasekara ShannonAmandaAmarasekara commented Jul 1, 2025 •

Copy link
Copy Markdown
Contributor

The gateway delete interceptor endpoint is being updated to receive the interceptor scope as optional. This PR is to update the logic of handling delete interceptor requests using the cli, to not set a default scope when no scope is provided.

Scenario:
Given a user has deployed an interceptor with no scope using the cli
When the user deletes this interceptor with no scope using the cli
Then the delete should succeed

Releasing (cli first or gateway?):
old cli + new gateway -> "Could not delete resource Interceptor/inject-header: Interceptor inject-header not found with scope {vCluster=null, group=null, username=null}"
new cli + old gateway -> Could not delete resource Interceptor/inject-header: Invalid value for: body (exhausted input)

  • Either way this fails but doesn't break anything as it's not working currently anyway

See the PR on the gateway:
https://github.com/conduktor/conduktor-proxy/pull/2581

Linear ticket:
https://linear.app/conduktor/issue/YSH-98/delete-interceptors-vcluster-null-inconsistency-with-put

Example with screenshots:
cli-commands-successful-delete-no-scope
interceptor-config

strokyl

This comment was marked as resolved.

Comment thread client/gateway_client.go Outdated
@ShannonAmandaAmarasekara
ShannonAmandaAmarasekara merged commit 4c7d7b6 into main Jul 4, 2025
@ShannonAmandaAmarasekara
ShannonAmandaAmarasekara deleted the YSH-98-remove-default-scope-delete branch July 4, 2025 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants