You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a Python-based implementation of the **BaSyx Asset Administration Shell (AAS) Discovery Service**.
4
-
It provides basic discovery functionality for AAS IDs and their corresponding assets, as specified in the official [Discovery Service Specification v3.1.0_SSP-001](https://app.swaggerhub.com/apis/Plattform_i40/DiscoveryServiceSpecification/V3.1.0_SSP-001).
4
+
It provides basic discovery functionality for AAS IDs and their corresponding assets, as specified in the official [Discovery Service Specification v3.1.1_SSP-001](https://app.swaggerhub.com/apis/Plattform_i40/DiscoveryServiceSpecification/V3.1.1_SSP-001).
5
5
6
6
## Overview
7
7
@@ -11,38 +11,36 @@ The Discovery Service stores and retrieves relations between AAS identifiers and
|**search_all_aas_ids_by_asset_link**| Find AAS identifiers by providing asset link values |`POST http://localhost:8084/api/v3.0/lookup/shellsByAssetLink`|
15
-
|**get_all_specific_asset_ids_by_aas_id**| Return specific asset ids associated with an AAS ID |`GET http://localhost:8084/api/v3.0/lookup/shells/{aasIdentifier}`|
16
-
|**post_all_asset_links_by_id**| Register specific asset ids linked to an AAS |`POST http://localhost:8084/api/v3.0/lookup/shells/{aasIdentifier}`|
17
-
|**delete_all_asset_links_by_id**| Delete all asset links associated with a specific AAS ID |`DELETE http://localhost:8084/api/v3.0/lookup/shells/{aasIdentifier}`|
18
-
|
14
+
|**get_description**| Return the supported Discovery Service profiles |`GET http://localhost:8084/api/v3.1/description`|
15
+
|**get_all_aas_ids_by_asset_link**| Find AAS identifiers by asset link query parameter |`GET http://localhost:8084/api/v3.1/lookup/shells?assetIds={assetIds}`|
16
+
|**search_all_aas_ids_by_asset_link**| Find AAS identifiers by providing asset link values |`POST http://localhost:8084/api/v3.1/lookup/shellsByAssetLink`|
17
+
|**get_all_specific_asset_ids_by_aas_id**| Return specific asset ids associated with an AAS ID |`GET http://localhost:8084/api/v3.1/lookup/shells/{aasIdentifier}`|
18
+
|**post_all_asset_links_by_id**| Register specific asset ids linked to an AAS |`POST http://localhost:8084/api/v3.1/lookup/shells/{aasIdentifier}`|
19
+
|**delete_all_asset_links_by_id**| Delete all asset links associated with a specific AAS ID |`DELETE http://localhost:8084/api/v3.1/lookup/shells/{aasIdentifier}`|
20
+
19
21
20
22
## Configuration
21
-
Add discovery_store as directory
22
-
The service can be configured to use either:
23
+
This example Docker compose configuration starts a discovery server.
24
+
25
+
The container image can also be built and run via:
26
+
```
27
+
$ docker compose up
28
+
```
23
29
24
-
-**In-memory storage** (default): Temporary data storage that resets on service restart.
25
-
-**MongoDB storage**: Persistent backend storage using MongoDB.
30
+
## Persistence
26
31
27
-
### Configuration via Environment Variables
32
+
The discovery service can run in persistent or non-persistent mode.
0 commit comments