Skip to content
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.

Sign up for GitHub

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

Jump to bottom

MVD Dependency Management #30

Open
7 tasks
zeier opened this issue May 30, 2022 · 1 comment
Open
7 tasks

MVD Dependency Management #30

zeier opened this issue May 30, 2022 · 1 comment
Labels
feature MVD on hold

Comments

@zeier
Copy link

zeier commented May 30, 2022 •
edited by Izzzu
Loading

Description

The MVD has dependencies to several components that reside in individual repositories:

  • Eclipse Dataspace Connector (incl. Federated Catalog)
  • EDC Data Dashboard
  • RegistryService
  • IdentityHub
  • MVD UI (will be created starting in August 2022)

The current approach is to check out and build the corresponding components when the MVD is deployed.

The goal of this feature is to define and implement a dependency management process, which leverages Maven artifacts at least for some of the dependencies. The dependency management process should allow to better manage dependencies once the basic components are in place.

The MVD should also use the published EDC artifacts, to demonstrate how ECD artefacts can be consumed.

Acceptance Criteria

  • Concept for dependency management is defined and documented
  • RegistryService and Identity Hub artefacts are published
  • MVD consumes artefacts from EDC, RegistryService and IdentityHub repositories

Stories
@ouphi ouphi mentioned this issue Jun 13, 2022
Open
4 tasks
@chrislomonico chrislomonico transferred this issue from agera-edc/MinimumViableDataspaceOld Jun 13, 2022
@zeier zeier moved this to Ready in Agera EDC Jun 22, 2022
This was referenced Jun 23, 2022
Open
Open
Open
Open
@zeier zeier removed the team review label Jun 30, 2022
@cpeeyush cpeeyush mentioned this issue Jul 4, 2022
Closed
@zeier zeier added the on hold label Jul 13, 2022
@zeier
Copy link
Author

zeier commented Jul 13, 2022

Put on hold, as it is projected to be too much scope for the team until end of August.
#36 and #157 have higher priority.
This item can be taken up again if there is capacity.

cpeeyush added a commit that referenced this issue Jul 27, 2022
@cpeeyush @Izzzu @zeier
Cloud Deployment: Fix MVD cloud deployment health check failure (#30)
9362f36 
* Cloud Deployment: Fix MVD cloud deployment health check failure (#217)

* Update liveness check

* Update liveness check

* Upgrade curl

* Update

* upgrade curl

* Update

* update liveness probe

* Update deployment/curl-upgrade.sh

Co-authored-by: Izabela Kulakowska <ikulakowska@microsoft.com>

* Fix typo

Co-authored-by: Izabela Kulakowska <ikulakowska@microsoft.com>
Co-authored-by: Max Zeier <33636338+zeier@users.noreply.github.com>

* terraform fmt

Co-authored-by: Izabela Kulakowska <ikulakowska@microsoft.com>
Co-authored-by: Max Zeier <33636338+zeier@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature MVD on hold
Projects
Agera EDC
Status: Ready
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zeier