The following changes are requests for enhancements discussed and raised with a business partner that is actively using our MAS cli.
This PR adds support for some additional Manage settings:
Base and secondary languages
Allow Manage dedicated Db2 instance to be configured with db2oltp type instead of default db2wh. The db2wh will continue to be the default option, although allowing db2oltp for Manage might be useful for customers using Manage & Cognos integration in the same database since Cognos does not support db2wh type.
Server timezone: Allow a timezone to be set at ManageWorkspace CR level with {{ mas_app_settings_server_timezone }} property. In addition, allow defining same value in spec.advOpts.timezone: {{ db2_timezone }} property for DB2Ucluster in db2 role. This way, both Manage server and the corresponding DB2 instance will be running within the same timezone.
The following changes are requests for enhancements discussed and raised with a business partner that is actively using our MAS cli.
This PR adds support for some additional Manage settings:
Base and secondary languages
db2oltptype instead of defaultdb2wh. Thedb2whwill continue to be the default option, although allowingdb2oltpfor Manage might be useful for customers using Manage & Cognos integration in the same database since Cognos does not supportdb2whtype.{{ mas_app_settings_server_timezone }}property. In addition, allow defining same value inspec.advOpts.timezone: {{ db2_timezone }}property forDB2Uclusterindb2role. This way, both Manage server and the corresponding DB2 instance will be running within the same timezone.Once this is merged, we need to merge MAS CLI PR: https://github.com/ibm-mas/cli/pull/854