Add Asset - API

[chrislomonico]

Feature agera-edc/MinimumViableDataspaceFork#59

after agera-edc/MinimumViableDataspaceFork#135

Description

As a dataspace participant I want to add a new asset in order to share it with other participants in a subsequent step.

This action refers to creating an Asset and a DataAddress (pointing to the physical location of the data item) in the participant's connector. At this time, other dataspace participants do not yet have access to the Asset, because no ContractDefinition exists yet (#9).

The following steps are necessary:

1. generate a DataAddress containing relevant information (bucket name, account name, etc.)
2. generate an Asset object describing the data item
3. call REST endpoint to insert the Asset/DataAddress tuple into the connector at POST /assets

In the first iteration of the MVD, composing the Asset/DataAddress is done through and aided by the connector's web UI using a simple text entry widget. So when the user selects AzureStorage the widget should only display input for those particular properties (Account, container, etc.).

Initially, we'll support the data address types AzureStorage (#6) and api with the following properties:

• type=AzureStorage: account name, container name
• type=api: URL

Note: Testing for AmazonS3 is out of scope for this story and should be shown as not supported

Note: The blob container to be added needs to exist prior to adding the asset.

Acceptance Criteria

• [ ] A web UI provides an easy and guided way to create DataAddress and Asset objects
• [ ] DataAddress and Asset objects can be uploaded to EDC via its REST API
• [ ] Documentation on how to upload new assets through the UI and REST API is available
• [ ] Assets can be uploaded based on step by step instructions without having deep technical expertise
• [ ] AmazonS3 is shown as not supported

Tasks

• [ ] Check if the current UI works with Asset API (only for api, Azure Storage is covered in agera-edc/MinimumViableDataspaceFork#135)
• [ ] Adapt the UI (Data Publisher tab) to match the dtos in the postman collection (if needed)
• [ ] Change the name of the Data Publisher tab to more meaningful name
• [ ] Add/update instructions in docs

[zeier]

Not planned to cover this item by the Agera crew until end of August.