Work out how to refresh staging from production

[john-gom]

No description provided.

[hangy]

Need to define if we need all data (all users and clients).

If we want all data from production to be copied to staging, including allowing existing data to be overridden, we can export the production realm with full data, and import to to staging manually, potentially after fixing some URLs. The Keycloak Admin UI warns about exporting realms with a lot of data, though. With all users from production, this could be a really heavy operation. (If it works at all, to be honest.)

[john-gom]

I'm not sure that we should be exporting real user data from production to staging at all. However, we need to come up with a strategy that copes with User.sto files as well in the short term. Do people think it would be a problem if production and staging had different logins / passwords?

[hangy]

A question might be how willing everyone is with users in test being very different from prod. I believe that everything is copied if OFF staging gets refreshed today.

Considering GDPR and similar regulations, it's probably better not to copy prod user data to staging.

@stephanegigandet Do you have a strong opinion about either option?

[john-gom]

One suggestion from @alexgarel is that we could generate fake accounts in Staging with a dummy email address but the same user id (as this is public anyway) and a special password, so no need to refer to the production data at all as we can just do this by listing the user.sto file names.

[alexgarel]

If ever we can report users properties (maybe reading sto) it would be better for reproducibility (but in no way mandatory).