Deck upstream with tags

During testing with Konnect and Deck the following error scenario has occured:

Updating a service on Konnect with deck results in an error in combination with upstreams and tags.

“code”: 9,
“message”: “listing resources scoped to a resource while applying a filter are not yet supported”

The call deck struggles with is:

When testing the same scenario with a local kong gateway (running the latest docker version) there is no problem updating the service with deck. We’ve tested the same call above (/upstreams?tags=tagid) which returns the expected upstream. Any idea what might cause this problem?


Unfortunately this is a known limitation and we are working to improve this tag mechanism with decK.