Class TeamStorageException
A team's underlying storage could not be removed. Carries the team key and the store's own failure as InnerException.
public sealed class TeamStorageException : Exception, ISerializable
- Inheritance
-
TeamStorageException
- Implements
- Inherited Members
Remarks
Exists so a deployment problem stops arriving as a driver stack trace. Purging a team in a
per-team-database deployment drops that database, and dropping a database is a privilege most managed
deployments do not give an application's data-plane user — in MongoDB Atlas, readWriteAnyDatabase
does not include dropDatabase. The refusal therefore comes from the store, one layer below
authorization, after every scope check has already passed.
The operator can do nothing about it from the UI, so the message names what the deployment has to grant rather than suggesting the caller lacks permission. Reported by Eplicta FortDocs (Tharga/Team#224), where a `MongoCommandException` reached the error page.
Thrown by the storage adapter, not by the domain. A missing scope is still UnauthorizedAccessException — the two are different failures with different fixes, and collapsing them would send an operator to the wrong place.
Constructors
TeamStorageException(string, string, Exception)
public TeamStorageException(string teamKey, string message, Exception innerException)
Parameters
teamKeystringThe team whose storage could not be removed.
messagestringWhat failed, and what a deployment must grant to make it work.
innerExceptionExceptionThe store's own exception, preserved for diagnostics.
Properties
TeamKey
The team whose storage could not be removed.
public string TeamKey { get; }