-
Bug
-
Resolution: Done
-
Critical
-
Compatibility/Configuration
When one wants to configure secured endpoint, the documented option is to use HTTPS_* variables https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.4/html-single/getting_started_with_jboss_eap_for_openshift_container_platform/index#https_env_variables
However, up until EAP 7.4 images, it also worked to use the same variables with EAP_ prefix (eg. EAP_HTTPS_KEYSTORE).
We happen to have some tests that are actually using those (probably) old variables which was working fine up until now. I haven't found any info they were deprecated/removed. I even found some tests for it https://github.com/jboss-container-images/jboss-eap-modules/blob/master/tests/features/https.feature
So given that it worked so far there might be some customers still using it (because migration wasn't needed) so we should deal with it somehow:
1) keep backward compatibility?
2) include migration instructions in RNs/migration guide because support for those was finally removed?
3) any other option?
Since it might be seen as a regression (but considering we document correct state) I am raising this as critical to get attention.