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
Our service definitions will include standard URLs for service access (HTTPS), but we have a set of consumers that accept a custom scheme. The custom scheme allows us to signal that service discovery should be used to resolve the full URL.
For my purposes, it's probably enough to use a plugin to modify the OpenAPI YAML/JSON output to include the additional URL, possibly using information from metadata? Looking at the core code, the validation would seem to exclude the idea of allowing additional schemes any other way, and I don't need to implement it in the Go client at this point.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Our service definitions will include standard URLs for service access (HTTPS), but we have a set of consumers that accept a custom scheme. The custom scheme allows us to signal that service discovery should be used to resolve the full URL.
For my purposes, it's probably enough to use a plugin to modify the OpenAPI YAML/JSON output to include the additional URL, possibly using information from metadata? Looking at the core code, the validation would seem to exclude the idea of allowing additional schemes any other way, and I don't need to implement it in the Go client at this point.
Any pointers on a good way to implement this?
Beta Was this translation helpful? Give feedback.
All reactions