"None" state store definitely would be good for one of our case - automatic preview deploys for pull requests. Statefull approach works good 99.9% of time but

"None" state store definitely would be good for one of our case - automatic preview deploys for pull requests. Statefull approach works good 99.9% of time but rare errors like inability to destroy resource because of cloud provider issues cause that you need manual interventions - i.e. resource cant be created as not managed by state etc. Even rare errors are not rare when you have 20+ devs :-) That needs some manual fixes i.e import state, killing resources etc but not all devs has access rights or knowledge to do this.