Auto override of settings MAAP extensions

[grallewellyn]

MAAP extensions are overriding other set settings which is causing problems in other hubs trying to use MAAP extensions
Disasters-Learning-Portal/disasters-product-algorithms#88

[wildintellect]

@marjo-luc what's the timeline for getting this patched? We want to make sure we can apply the fix to non-MAAP hubs this month, and incorporate into the end of September target release of new images. Other hubs are likely going to directly pull MAAP images once this is fixed, since it will work on non-MAAP hubs too.

[marjo-luc]

@wildintellect I've made the following updates to the MAAP Jupyterlab extensions:

• Point to the OPS MAAP API by default
• Link to retrieve user token now directs user to the new console

These updates should address the "stickiness" described in Disasters-Learning-Portal/disasters-product-algorithms#88. As for surviving reboots, I need some clarification so I can properly test this: looking through slack and the messages in the ticket linked to above, you're able to enter the API URL and your token into the MAAP jupyter extension settings page, and they survive through a reboot of the same image, correct? But you are losing non-MAAP user settings -- is that correct?

These changes apply to the following three MAAP Jupyterlab extensions:

• algorithms-jupyter-extension
• jupyter-server-extension
• dps-jupyter-extension

[wildintellect]

@marjo-luc no, the maap user settings are lost (API and Token), if the image on next boot has the MAAP extension. It's only preserved if for some reason on next boot I pick a non-MAAP extension image. So the extension is overriding it's own settings.

[marjo-luc]

@wildintellect I have an image built containing the fix. It works as expected locally and on MAAP Hub. Could you point me to a non-MAAP Hub that I could test against?

[wildintellect]

https://hub.openveda.cloud cc: @slesaad @anayeaye in case someone needs to approve your account (I think I can)