-
Type:
Bug
-
Status: Verified (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 7.1.0.GA
-
Component/s: Cloud, Configuration
-
Labels:
-
Target Release:
-
Affects:Documentation (Ref Guide, User Guide, etc.), Release Notes
-
Release Notes Text:PRS 89 and 119 merged.
-
Sprint:2018 Week 36-38
This template missed and/or misconfigured several config points, including https support and certain database properties:
- rhdm71-optaweb-employee-rostering-externaldb.yaml
These templates were completely missing:
- rhdm71-optaweb-employee-rostering-mysql.yaml
- rhdm71-optaweb-employee-rostering-postgresql.yaml
- rhdm71-optaweb-employee-trial-ephemeral.yaml
- follows up on
-
RHDM-727 rename RHDM optaweb to optaweb-employee-rostering
-
- Verified
-
-
RHDM-697 CE build alignment for EAP-based OpenShift images in RHDM
-
- Verified
-
-
RHDM-670 Update RHDM Templates to be in a similar structure as RHPAM Templates
-
- Verified
-
- is related to
-
PLANNER-1221 OptaWeb Employee Rostering: docker image has a slow startup time with MySql DB
-
- Resolved
-
-
RHDM-745 Product build: optaweb-employeer-rostering war file (should not) need 2 variants: normal *.war and *-openshift.war
-
- New
-
-
PLANNER-1279 OptaWeb Employee Rostering should allow modifying the log level to reduce log verbosity in production
-
- Open
-
-
PLANNER-1278 OptaWeb Employee Rostering should expose system property org.optaweb.employeerostering.persistence.hbm2ddl.auto and set it to update if -P openshift is active
-
- Resolved
-