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
In proxy discovery mode, we noticed that proxies with a reference to a spec (association.json) were correctly discovered as "oas" services.
However, it appears that, without altering any of the already discovered proxies/specs, subsequent API service revisions are created with an "unstructured" format as shown below :
The text was updated successfully, but these errors were encountered:
This seems to be a logic error. When the call to get the spec file does not fail, but the data returned when getting the spec seems to be bad or empty, we were publishing the API. Will skip publishing in this case.
Hi,
In proxy discovery mode, we noticed that proxies with a reference to a spec (association.json) were correctly discovered as "oas" services.
However, it appears that, without altering any of the already discovered proxies/specs, subsequent API service revisions are created with an "unstructured" format as shown below :
The text was updated successfully, but these errors were encountered: