Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Work out how to refresh staging from production #35

Open
john-gom opened this issue Jun 28, 2024 · 5 comments
Open

Work out how to refresh staging from production #35

john-gom opened this issue Jun 28, 2024 · 5 comments

Comments

@john-gom
Copy link
Collaborator

No description provided.

@hangy
Copy link
Member

hangy commented Jul 28, 2024

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
Copy link
Collaborator Author

john-gom commented Aug 2, 2024

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
Copy link
Member

hangy commented Aug 2, 2024

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
Copy link
Collaborator Author

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
Copy link
Member

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

hangy added a commit to openfoodfacts/openfoodfacts-server that referenced this issue Sep 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: First release
Development

No branches or pull requests

3 participants