Paul Lorenz

https://goreleaser.com/customization/universalbinaries/ might be helpful here

> @dovholuknf @plorenz I'd be interested in contributing this if you are able to give me some direction and coaching. Sure, seems like a nice, user-friendly feature :+1:

This is a bit tricky. We have the specs, they just live in their respective repos: * edge client: https://github.com/openziti/edge/blob/main/specs/client.yml * edge mgmt: https://github.com/openziti/edge/blob/main/specs/management.yml * fabric mgmt: https://github.com/openziti/fabric/blob/main/specs/swagger.yml The tricky...

@qrkourier sure, if you think that's useful. The ziti binary has the specs embedded in it, so it could just spit them out. Or it could call out to a...

> @plorenz If I understood correctly that means I could get the spec for a particular API version by running the `ziti` CLI of the same version, after the get...

I don't have any objections if @dovholuknf doesn't

It's not used in production systems, but I believe startup will fail if it's not specified. It's still used by some ATs in the fabric, which I'm working on updating...

Can you add a note to the changelog as well, please?

Hi @mikegorman-nf is this on the client or server side? Do you know which component is involved? Tunneler, ER/T, etc?

@mikegorman-nf is this a duplicate of openziti/edge#1503 ?