Provide documentation for the expected structure of a template container

microsoft / FHIR-Converter

Conversion utility to translate legacy data formats into FHIR

MIT License

399 stars 175 forks source link

Provide documentation for the expected structure of a template container #560

Closed liammoat closed 3 months ago

liammoat commented 4 months ago

The fhir-converter service has support for using Azure Storage as a custom template library.

However, to my knowledge, we do not provide documentation for the structure of the storage container. For example, should we upload raw .liquid files, should they be archived in a .tar.gz or something else?

ShaunDonn2 commented 4 months ago

Thanks @liammoat for the feedback. Will update the docs. To quickly unblock anybody who has an issue related to this in the meantime, the container should contain the raw .liquid files. These can be organized into directories, but the path to the template within the container will have to be specified in the RootTemplateName request field.