Hide Forgot
Description of problem: It's not very user friendly that user needs to configure 3 config files (dtgov.properties, dtgov-ui.properties & s-ramp-ui.properties) in order to get design-time governance working at non-default location (other than http://localhost:8080/*). Suggested improvement: Such distributed configuration supports various deployment schemas, which should be preserved but the default configuration could be taken from server variables like ${jboss.bind.address}:8080 + ${jboss.socket.binding.port-offset}/<war_name> to create appropriate urls that are needed for web applications. Only if user set these urls explicitly in config files (templates should be included) are these urls taken into account. To sum up: * no urls in configs -> expect gov app running at default locations: ${jboss.bind.address}:8080 + ${jboss.socket.binding.port-offset}/<war_name> * urls explicitly set in config files -> use urls specified in config files Version-Release number of selected component (if applicable): * FSW 6.0.0.ER6 (Beta) How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Once I ran standalone.sh -b <some_ip> it will run on this ip and no additional manual configuration won't be necessary. Only if running in non-default deployment configuration like running sramp repository at different location to dtgov or even dtgov-ui on different node to dtgov task-api endpoint, etc., should be user forced to specify these urls explicitly. Additional info:
I was just about the merge in the fix. So I should not do this now?
This is not a blocker for the release so should not be merged into the product branch at this time.
Fix is ready to go, but is not merged into the prod branch. To apply the fix merge these 3 transactions: 1. overlord-commons: https://github.com/Governance/overlord-commons/commit/743341048738e240b23263c38c8af5aac7c677a4 with id 743341048738e240b23263c38c8af5aac7c677a4 2. s-ramp: https://github.com/Governance/s-ramp/commit/acf98a659606288b6a9f224263afa46fefef3e60 with id acf98a659606288b6a9f224263afa46fefef3e60 3. dtgov: https://github.com/Governance/dtgov/commit/8cd9c47d2cdb723abcbefdec1b20394e2478428d with id 8cd9c47d2cdb723abcbefdec1b20394e2478428d
It's not a blocker, however, extremely user unfriendly. Let's say user wants to set up a cluster consisting of 5 nodes and he has to configure 15 files, instead of just running standalone.sh with a '-b' option. Fix is ready, please reconsider, setting blocker flag.
*** Bug 1029922 has been marked as a duplicate of this bug. ***
Verified in FSW 6.0.0.ER8