Create new Component "AAS Gateway"

[FriedJannik]

This is the main Ticket It is split into Sub-Tickets

Idea

Allow distribution of AAS/SM Descriptors in different Registries as well as AASs and Submodels to be placed in distributed Repositories when using the preconfiguration feature or the upload endpoint. When using the upload endpoint, SM Descriptors should also be present in the AAS Registry. When executing DELETE requests on the registry the user should be able to determine, if Submodels/AAS should also be deleted. The default is configurable in application.properties

Affected API Endpoints

• POST /shells
• PUT /shells/{aasIdentifier} (relevant when updating SM references when SM Descriptors are Part of the AAS Registry, could be problematic)
• POST /shells/{aasIdentifier} (relevant when updating SM references when SM Descriptors are Part of the AAS Registry, could be problematic)
• DELETE /shells/{aasIdentifier}/submodel-refs/{submodelIdentifier} (could be problematic)
• DELETE /shell-descriptors/{aasIdentifier}
• POST /submodels
• DELETE /submodel-descriptors/{submodelIdentifier}

Approach

New client component that has its own API. This client component will be located in-between the standardized BaSyx components and the User/UI. The API will include the following endpoints

• POST /shells (enhancement of the standardized AAS Repository endpoint)
• PUT /shells/{aasIdentifier} (enhancement)
• DELETE /shells/{aasIdentifier} (enhancement)
• POST /submodels (enhancement)
• DELETE /submodels/{submodelIdentifier} (enhancement)
• POST /upload (new non standardized endpoint)