Dataplane Signaling Register endpoint is missing in V4 mgmt openapi schema

[perher]

Bug Report

Describe the Bug

The PUT /v4/dataplanes endpoint is missing in the Management API openapi schema under Dataplane Signaling Registration v4. As seen here https://eclipse-edc.github.io/Connector/openapi/management-api/ , only the DELETE endpoint is visible.

Expected Behavior

Both the PUT and DELETE endpoints to be visible as defined here https://github.com/eclipse-edc/Connector/blob/main/data-protocols/data-plane-signaling/data-plane-signaling-core/src/main/java/org/eclipse/edc/signaling/port/api/management/DataPlaneRegistrationApiV4.java#L35

Observed Behavior

Only the DELETE endpoint is shown

Steps to Reproduce

Steps to reproduce the behavior:

1. Go to https://eclipse-edc.github.io/Connector/openapi/management-api/#/Dataplane%20Signaling%20Registration%20v4
2. Click on Dataplane Signaling Registration v4 group.
3. Observe that only DELETE /v4/dataplanes/{dataplaneId} entry is defined.

Detailed Description

Might be some openapi spec merging issue as the Dataplane Selector v4 also defines endpoints under the /v4/dataplanes url?

[ndr-brt]

thanks for reporting. could be an issue with merging indeed

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[shardool-patil]

Hi @perher @ndr-brt,

If this issue is still open and hasn't been assigned yet, I would be happy to contribute. Please feel free to assign it to me.

Thank you!

[ndr-brt]

@perher I checked the documentation again, and it looks fixed now, likely this happened by just upgrading the plugins that are taking care to generate and merge the specs.

this can be closed, thanks anyway :)

[perher]

@ndr-brt yes agreed, original issue seems to be solved now. I noticed that the Dataplane Selector v4 API that I initially mentioned conflicting with this API is not shown anymore, but that might be expected?

[ndr-brt]

good catch, looks like PUT now "wins" over GET, so this is still an issue, though from a different perspective. will open the issue again