-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
None
-
Unset
-
None
-
-
After generating the new javascript-client, the v2 endpoint came back like this EndpointResourceV2$V2_getEndpoints vs the v1 that looks like EndpointResource$V1_getEndpoints. It seems the V2$V2 is an operation ID and while this is not blocking any work let's fix it as the openapi specs are used/seen by our customers
for more context – See v2 openapi.json file and search for getEndpoint. Notice the EndpointResourceV2$V2_getEndpoints.
Compare with v1 openapi.json file and search for getEndpoint. Notice EndpointResource$V1_getEndpoints.
- is depended on by
-
RHCLOUD-44313 Update js-clients for integrations and notifications
-
- New
-
- relates to
-
RHCLOUD-44122 Update notifications in js-clients
-
- Closed
-
- mentioned on