Add operationID field to tap openapi response

[kleimkuhler]

This fixes an issue users are experiencing when upgrading from from Linkerd
2.6 to 2.7 and use the kubernetes-external-secrets project.

The change introduced by #3700 resulted in the tap service showing up in the
/openapi/v2 API response. I confirmed this with a local build.

A dependency within the project expects the operationID field to be present
in the swagger definition. It is optional as stated in the
spec. It's
purpose is to identify an operation and should be unique.

This change adds that field to tap service swagger spec. While this can be
fixed in the KES dependency, it certainly does not hurt to add and other
libraries may similarly expect this field.

Signed-off-by: Kevin Leimkuhler [email protected]

[kleimkuhler]

#4209 asks for a different solution, but the issue that is being discussed on it is closed by this change. I don't know if we still need to worry about adding a /swaggerapi route to the tap service.

[cpretzer]

Nice fix @kleimkuhler

Small nit: I'd put this above Responses, just to make it a bit more readable, but TIOLI 👍

[cpretzer]

forgot to mention that this works for me locally :)

[mycrEEpy]

Is there a chance to cherry pick this into a 2.7.2 release?

[grampelberg]

@mycrEEpy we're not planning on a 2.7.2 right now. Doing stable releases takes a ton of effort and we've reserved those for critical proxy bugs so far (avoiding backporting any control plane changes). Is there something blocking you from picking up tomorrow's edge? 2.8 will be out in ~4 weeks as well (don't quote me on that).