You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the value of service.routes[*].plugins[*].service is set to the same service in which the route is nested, applying the configuration returns an entity already exists error.
For example, consider the following configuration:
Applying it succeeds first time, but fails second time with an entity already exists error. Deleting the plugin manually from the service then re-applying works, but still fails on the next apply with the same issue.
Options:
Completely ignore service field in plugins under a route which is explicitly defined under a service
Validate that the service field for the plugin matches the service name under which the route is nested, otherwise return a validation error
The text was updated successfully, but these errors were encountered:
Can you help us understand how you landed on this configuration?
[noob kong user here] while working on the config above I wanted to add a request-transformer plugin to a route nested within a service definition so I went to https://docs.konghq.com/hub/kong-inc/request-transformer/how-to/basic-example/ and copied the declarative example under Enable on a service which starts with:
If the value of
service.routes[*].plugins[*].service
is set to the same service in which the route is nested, applying the configuration returns anentity already exists
error.For example, consider the following configuration:
Applying it succeeds first time, but fails second time with an
entity already exists error
. Deleting the plugin manually from the service then re-applying works, but still fails on the next apply with the same issue.Options:
service
field in plugins under a route which is explicitly defined under a serviceservice
field for the plugin matches the service name under which the route is nested, otherwise return a validation errorThe text was updated successfully, but these errors were encountered: