Lee Surprenant

> It appears to be licensed until Creative Commons 4.0, so technically we could redistribute it. That was basically my thought...include it right in this repo and use it conditionally....

possibly duplicated by https://github.com/eclipse-openj9/openj9/issues/14717 (which has more discussion)

https://hub.docker.com/_/microsoft-azure-storage-azurite still lists x86_64 as the only supported architecture, but I was somehow able to run it on my new MacBook Pro M1 with colima + docker... maybe its already...

Even if we don't implement this, maybe we should introduce a config option to throw an error if someone specifies a securityContext that we don't support?

Decision: implement as suggested above and make that the default (secure by default) > introduce a config option to throw an error if someone specifies a securityContext that we don't...

notes on introducing a new config parameter: * constant in FHIRConfiguration * use FHIRConfigHelper to read the value (with optional default value) * document in FHIRServerUserGuide section 5.1 (3 tables)...

We saw this when using our ibm-fhir-server helm chart to deploy fhir-server and postgres to a kubernetes cluster, then ran the tool against the db (using the admin user).

`/opt/wlp/usr/servers/defaultServer` is the default `server.output.dir` in liberty, so its not an unreasonable default. the reason I made `build/boostrap_derby.sh` default to `${WORKSPACE}/derby` (where WORKSPACE is the directory you've cloned/extracted the project...

In the container image, the liberty output directory is actually at `/opt/ol/wlp/output/defaultServer` (and thus this is where derby will live on the container), so maybe it makes the most sense...

from our install script, we create a directory called 'wlp'. current behavior: * if invoked like `./install.sh dir1` it creates the server under `dir1/wlp` * if invoked like `./install.sh` it...