-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: split data plane module into two separate modules #3676
refactor: split data plane module into two separate modules #3676
Conversation
# Conflicts: # spi/common/core-spi/src/main/java/org/eclipse/edc/spi/monitor/Monitor.java # spi/common/core-spi/src/main/java/org/eclipse/edc/spi/monitor/PrefixMonitor.java
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #3676 +/- ##
==========================================
- Coverage 71.73% 71.72% -0.02%
==========================================
Files 919 919
Lines 18465 18468 +3
Branches 1034 1034
==========================================
Hits 13246 13246
- Misses 4760 4763 +3
Partials 459 459 ☔ View full report in Codecov by Sentry. |
…_api_context_into_dedicated_swagger_hub_page
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we please break this into two PRs because the module shift has implications for downstream repositories and is not a "doc" change?
The creation of the new public hub & split of the modules is the minimum requirement for this PR |
We are not releasing the doc at this point. The two changes are distinct, particularly because the module split has significant downstream implications. Please make these changes in two separate PRs so that they can be reviewed and documented correctly. |
…into_dedicated_swagger_hub_page' into docs/publish_public_api_context_into_dedicated_swagger_hub_page # Conflicts: # extensions/data-plane/data-plane-control-api/README.md # extensions/data-plane/data-plane-public-api/README.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR does not appear to break out the changes into two PRs as requested (at least the title does not indicate that, and my issue was not marked as resolved).
Please put the module refactor in its own PR.
…_api_context_into_dedicated_swagger_hub_page
This PR is now solely responsible for the module migration I'm unable to resolve your comment tho |
What this PR changes/adds
data-plane-api
module into two separate modulesdata-plane-control-api
&data-plane-public-api
data-plane-public-api
module topublic-api
groupWhy it does that
Interfaces under
data-plane-public-api
should not be undercontrol-api
api group because this api group is intended for internal communication.Further notes
This introduces a breaking change because the
data-plane-api
module has been split intodata-plane-control-api
anddata-plane-public-api
. Downstream projects need to adjust their dependencies.Note that the migration of the
data-plane-api
README file will be handled in a separate PR.Linked Issue(s)
Closes #3373
Depends on #3686