AssetPermissionsConflictError

Thrown by the asset permission mutation methods on a 409, which on this surface is always an etag failure:

• EtagMismatch — the etag is stale; re-read (or use currentState) and retry. Expect this routinely: the scope's etag is customer-wide, so any administrator's write invalidates it.
• EtagRequired — the write omitted an etag but the principal already held capabilities, so it would have replaced state the caller never read.

Hierarchy

• Error
  • AssetPermissionsConflictError

Index

Constructors

• constructor

Properties

• conflictCause
• currentState
• errorBody

Constructors

constructor

• new AssetPermissionsConflictError(message: string, errorBody: AssetPermissionsConflictErrorBody): AssetPermissionsConflictError

• Overrides Error.constructor

  Parameters

  • message: string

  • errorBody: AssetPermissionsConflictErrorBody

  Returns AssetPermissionsConflictError

Properties

publicreadonlyconflictCause

conflictCause: TwinPermissionsConflictCause

Which of the two conflicts this is. Named conflictCause rather than cause so the standard Error.cause — whose consumers expect a wrapped error, not a string — is left alone.

publicoptionalreadonlycurrentState

currentState?: AssetPrincipalPermissionsGet

The entry as the server holds it, including the etag to retry with.

publicreadonlyerrorBody

errorBody: AssetPermissionsConflictErrorBody