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
I installed the registry following the INSTALL.md on minikube. After applying the change as stated in PR #118, I get it running and can also call the swagger ui on https://minikube/semantics/registry.
The registry also works. For example, I can test an API endpoint with curl: curl -X 'GET' 'https://minikube/semantics/registry/registry/shell-descriptors?page=0&pageSize=10' -H 'accept: application/json' --insecure
However, if I do the same from the swagger ui, it fails as the base path (i.e., /semantics/registry) is not taken into account on the swagger ui.
I installed the registry following the INSTALL.md on minikube. After applying the change as stated in PR #118, I get it running and can also call the swagger ui on https://minikube/semantics/registry.
The registry also works. For example, I can test an API endpoint with curl:
curl -X 'GET' 'https://minikube/semantics/registry/registry/shell-descriptors?page=0&pageSize=10' -H 'accept: application/json' --insecure
However, if I do the same from the swagger ui, it fails as the base path (i.e.,
/semantics/registry
) is not taken into account on the swagger ui.So, I am wondering if it might be a solution to add the
basePath
to thebackend/src/main/resources/static/aas-registry-openapi.yaml
as described here: https://swagger.io/docs/specification/2-0/api-host-and-base-path/The same issue also seems to be present on the CX INT registry: https://semantics.int.demo.catena-x.net/registry/swagger-ui/index.html. There, the basePath
/registry
is also not taken into account by the swagger ui (as it is not defined in the openapi.yaml).If my thoughts are not correct, I appreciate any other help to set up the registry with a working swagger ui.
The text was updated successfully, but these errors were encountered: