Paul Tiplady

Pre-Django 2.1 there wasn't a built-in "read-only" permission. The framework chooses "fail-open" instead of "fail-close" here, which isn't the default that I'd expect; however now that there is an explicit...

Breaking back-compat might not be desirable; if so would it be worth adding a subclass that does respect the permission? Something like this would be an option: ``` class DjangoModelPermissionsStrict(DjangoModelPermissions):...

I'd like to add a different use-case example for this feature request. I use review apps. I create a fresh namespace & copy of my app per Pull Request. I...

@WoodyWoodsta given that you can enable [Encryption at Rest](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/) to set up KEK/DED layered encryption for Secrets (much as Vault does), what's the problem with Secrets? My understanding is that...

> If you were to then decide to create certificates at the root namespace I think the Hierarchical Namespace approach in general would be something like: ``` team1/Certificate team1/test-env-1/Ingress team1/test-env-2/Ingress...

This has been the biggest pain point for me coming from Django's UnitTest class-based tests, to pytest-django -- in Django we use `setUpTestData` to run expensive DB operations once (equivalent...

Thanks for the additional detail @cybergrind. I've dug into this a little bit more, but have run out of time for today -- here's where I've got to, I'd appreciate...

#33 is closed, and #388 contains no meaningful discussion (unlike this one). Seems odd to close this one @blueyed , if anything I'd suggest closing #388 and make this one...

👍 thanks!

Just checking back in here -- still an issue, and I haven't had time to dig in further. However there has been a bit of movement upstream - there's now...