the expected way to define datasources is to do what the
template example I provided does, in which case the image will
actually generate the entire datasource definition for you.
not sure if the v3 images have the same behavior as v2 with
respect to env variables (in v2 we would scan the entire app
server config file for any references to an env variable, and
perform substitution). I thought that behavior was carried to
v3, but not sure and maybe there are only some files it scans
and some it doesn't.
Cernich might be able to shed more light on the expected