In marain-dotnet/Marain.UserNotifications#112 it became apparent that we have a global lack of clarity around expected error handling behaviour in cases where the requested container cannot be created for some reason.
There are at least two different reasons this could happen:
- transient infrastructure failure
- incorrect configuration
The documentation for all of our tenanted storage providers says nothing about how to distinguish between these. This had percolated up the stack causing the same essential problem to become visible in the PR in Marain.UserNotifications. But that PR can't solve that problem on its own. It first needs to be addressed at the Corvus.Tenancy level, and once we've established the pattern here, that will have knock-on consequences for anything that consumes this.
In marain-dotnet/Marain.UserNotifications#112 it became apparent that we have a global lack of clarity around expected error handling behaviour in cases where the requested container cannot be created for some reason.
There are at least two different reasons this could happen:
The documentation for all of our tenanted storage providers says nothing about how to distinguish between these. This had percolated up the stack causing the same essential problem to become visible in the PR in
Marain.UserNotifications. But that PR can't solve that problem on its own. It first needs to be addressed at theCorvus.Tenancylevel, and once we've established the pattern here, that will have knock-on consequences for anything that consumes this.