Configuration files are not directly compatible with pygeoapi.

Background

The configuration files in this repo use of a custom format, which combined a base configuration, with a server specific configuration to generate a pygeoapi formatted yml file. Our configuration pattern also includes logic for adding additional/overriding dependencies. The base configuration file and server specific file are combined within the image by the config_maker.py logic.

The challenge

The current pattern, valid pygeoapi formatted configuration files are created within the image, means that the file is not easily accessible outside of the images. This has several implications.

• More difficult to debug configuration. Viewing the final configuration requires building the image, starting the container, and inspecting the container's files.
• More difficult to test with other version of pygeoapi, or external/development versions of pygeoapi.
• More difficult to create custom configurations. Our custom format is similar but does not exactly align with pygeoapi's. User's wishing to tested with a custom or stripped down version of the configuration need to use a customized format rather than reference pygeoapi's documentation.

Closure Criteria

• We have evaluated and documented if the custom configuration benefits outweigh the negative impacts.
• We have implemented an applicable solution based on that evaluation.