And I look at the logs of my rate limiter:
You can see that it is getting (generic_key, testValue), you would expect: (testKey, testValue). The request_headers mapping is working as expected.
To Reproduce
Steps to reproduce the behavior:
Install emissary
Add the quote service the same as in the tutorial
Add the mapping as shown above (maybe without the ambassador-id and remove the namespace)
Add your RateLimiter of choice (I used the rate limit of Lyft) to see the output of the keys.
Versions (please complete the following information):
Ambassador: 3.1
Minikube with kubernetes V1.21
Additional context
For me this fortunately is not a big issue, as I only wanted to have 1 generic key anyway, but I'd imagine that this can be a very annoying bug if you want multiple generic keys.
Describe the bug The generic_key label in emissary-ingress is not attaching the correct key as a descriptor.
According to the docs you would expect: But when I apply this mapping:
And I look at the logs of my rate limiter: You can see that it is getting (generic_key, testValue), you would expect: (testKey, testValue). The request_headers mapping is working as expected.
To Reproduce Steps to reproduce the behavior:
Expected behavior I'd expect (testKey, testValue).
Versions (please complete the following information):
Additional context For me this fortunately is not a big issue, as I only wanted to have 1 generic key anyway, but I'd imagine that this can be a very annoying bug if you want multiple generic keys.