search

onaio / fhir-tooling

A command line utility to support FHIR Core content authoring
Other
1 stars 1 forks source link

Use the same config file for both the importer and efsity tools #192

Open Wambere opened 1 month ago

Wambere commented 1 month ago

When setting up a new project, you need to use the importer to setup keycloak/create users/upload content, then you need to use efsity to validate and publish configs. At the moment the importer uses a config.py file for configs while efsity uses an env.properties file, both of which have more or less the same content. Is it possible to just have one env file and use it for both?

pld commented 1 month ago

makes sense, probably easier to have the importer use the env.properties since Java is (imo) more picky about paths