1
When a production error occurs, the programmer needs to simulate the error to correct it. But I don’t want the developer to have access to all production data.
The solution I thought was to have a specific dump engine, where I’d dump a dump by changing users' emails, which is what would really be confidential.
Has anyone ever thought of solutions to this? Could they share their experiences?
0
What is customary for some companies to do is:
The approach depends on which problem you have at hand. Sometimes a problem that occurs in production, will not/would be possible to reproduce in demo, or at least would require a very large job. Now you can really follow this approach of creating a production dump and changing sensitive data, but in some cases this may not be enough for playback of the bug.
Browser other questions tagged django
You are not signed in. Login or sign up in order to post.
Yes. In my current context dev is the demo you mentioned. The sandbox is a problem. There are bugs that you really need to get the exact context that took place in Prod to evaluate. So I thought I’d dump the users' emails, keep it quiet. However I cannot understand how this might not be enough to reproduce the bug.
– Karl Zillner
I also have doubts about the best practices and/or solutions already developed specifically for this context.
– Karl Zillner
An odd example for the email case, but that has already happened where I work, is for the user to have 2 different emails in a place where they should be the same (different models). This in a dump that alters emails, can make it difficult. That is why companies that go the way of a sandbox with production data always have very specific and rigid NDA contracts.
– mazulo
Good practices and solutions depend on which approach Oce will choose. But something that is very practical and has been well used are CI/CD tools, like Jenkins, which does all this work for Oce after a push/deploy
– mazulo