[bug]: Infra config does not reload anymore about hoppscotch HOT 5 OPEN

@balub can you look into this?

from hoppscotch.

If the client secret changes on openid provider side, you couldn't login to admin dashboard to change the client secret on hoppscotch side.

from hoppscotch.

Related to #3868 btw

from hoppscotch.

Hey, @Breee so the way the InfraConfig works is that when the Hoppscotch instance is up for the first time we essentially read the env values and save them in the DB. Every subsequent time when the instance is spun up we check to see if any new env variable/s have been added and if yes we add them to the table. For the most part, once the values are loaded into the table, we do not check to see if values have changed to update their values to their new ones in the DB from the env file.

Instead, we recommend users update values from the admin dashboard. In your case, the recommended approach is to update the client secrets from the admin dashboard itself. Now one more thing to note is that just changing the values in the DB will not result in them being used in the Hoppscotch instance. To do that you will have to restart the instance so that all the modules can re-initialize themselves.

Updating values from the admin dashboard does all this so that once a value for a property has been updated, its new value is saved in the DB and the Hoppscotch instance uses the new values.

from hoppscotch.

We rely on fully automated updates with automated tests and rotate secrets frequently, so clicking in the UI is not a solution for us.

In my opinion cloud native applications should be fully configurable via ENV variables, config files or via API, everything else is broken by design.

A possible solution could be to calculate a delta of the ENV variables to what is in the DB and set them on startup. That is just a Single loop that solves my Problem. wdyt?

from hoppscotch.