Sorry, I forgot to answer about the loaddata proposal. So, loaddata will not do user removal for one thing.
About user creation, the process we have is: - add the user to the users list, - set the password in `ansible-vault create passwords/username` - CM will execute createsuperuser for users, >From that, it should maintain the userbase, on an ootb django project. The workflow you are suggesting is: - add the user to the users list, - set the password in `ansible-vault create passwords/username`, - somehow parse the settings to know the user model, - generate a json file with the users, and hope that it will work with their model, - use a script that django doesn't have to generate a salted password, - upload the script and apply it. I don't think I want my automation steps to rely on hope. What about the debugging process of such a complex implementation for such a simple task ? The cost is not worth the benefit. Injecting code in django-admin shell still does the same with a much cheaper complexity cost. Have a great day. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op19o1wUCd4CSvxHLKHAdBduPOO4H6PuhtuyZc_LYBO9ooA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
