Updating the ServiceControl connection doesn't change it for all users

[kbaley]

Describe the bug

Description

When you change the connection URL for ServiceControl in the configuration page, it updates the value in local storage for that browser but not for all users.

To duplicate (assuming there are two SC instances available:

1. Open the ServicePulse configuration page to the connections tab in a browser window
2. Open the same page in a private browser window
3. Change the value in the private browser window
4. Refresh the private browser window to verify the change saved
5. Refresh the main browser window

Expected behavior

The ServiceControl URL should be updated

Actual behavior

The private browser window will continue to use the new connection URL. The main browser window will use the old one.

Versions

Confirmed in version 1.37

Please list the version of the relevant packages or applications in which the bug exists.

Steps to reproduce

1. Open the ServicePulse configuration page to the connections tab in a browser window
2. Open the same page in a private browser window
3. Change the value in the private browser window
4. Refresh the private browser window to verify the change saved
5. Refresh the main browser window

Relevant log output

No response

Additional Information

Workarounds

Possible solutions

Additional information

[kbaley]

The way this works can be useful for users that want to change their connection to different instances of ServiceControl without affecting other users but it can also be confusing for ops folks that change the value thinking they are updating it for their entire team. At the very least, there should perhaps be some instructions on the page to the effect of:

This setting changes the connection only for this browser instance. To change this for all users, see the documentation

And include a link to our docs showing how to locate and update the app.constants.js file.

Or more ideally, fully support multiple instances of ServiceControl