Open david-i-berry opened 2 months ago
@david-i-berry do we have an example of a misconfigured collection or process? We can also look into the root cause of such misconfiguration.
Having said this, canning the OpenAPI document is a common pattern for deployments whose configurations only change on a release.
@tomkralidis @maaikelimper bumping this issue again.
By canning do you mean throwing away or having a pre canned version of the file? I was interpreting canning as throwing away.
Sorry @david-i-berry pre canned (as opposed to binning :) )
If a collection or process is misconfigured in the
pygeoapi-config.yml
theentrypoint.sh
script fails and thewis2box-api
container fails to start. This is due to https://github.com/wmo-im/wis2box-api/blob/9032a79981098ac368baab3dd9eae1d636677c5c/docker/entrypoint.sh#L61 and the generation of theopenapi-config.yml
file.This makes it challenging for users to maintain their collections (and any process plugins), with the container broken on restart if an error is made. This is unnecessary and could be avoided by providing a default
openapi-config.yml
and updating theopenapi-config.yml
manually. Instructions are provided as part of pygeoapi: https://docs.pygeoapi.io/en/stable/administration.html#creating-the-openapi-document and this could be part of the system configuration instructions / steps.Proposed solution:
openapi-config.yml
document in the repository / container image.openapi-config.yml
from theentrypoint.sh
.openapi-config.yml
file in the wis2box documentation (incl. validation).openapi-config.yml
when a new collection is added via the metadata editor.