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
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?
The text was updated successfully, but these errors were encountered:
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.
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?The text was updated successfully, but these errors were encountered: