This may not be feasible; reasons explained below.

If the user sets the env vars that trigger creation of a datasource resource, and that resource points to the will-no-longer-automatically-be-available org.postgresql and com.mysql drivers, have the script doing the processing log a deprecation WARN.

This might not be feasible because it's possible the user brought their own standalone-openshift.xml and aren't relying on us, or they may have configured the driver themselves in s2i.

But probably it's ok; we're talking about images where we ship the relevant modules ourselves, so if the user is using those modules, the warn is appropriate, regardless of how the xml config referencing them gets there. The trick is knowing they config is pointing at our modules, not some other differently-name module they may have installed themselves.