Check out v4 of the Fauna CLI
v4 of the Fauna CLI is now in beta. The new version introduces enhancements to the developer experience, including an improved authentication workflow. To get started, check out the CLI v4 quick start. |
accessProvider.delete()
Learn: Access providers |
---|
We recommend you use FSL to create and update access providers. See FSL access provider schema. |
Delete an access provider.
Description
Deletes an
AccessProvider
document.
AccessProvider
documents are FQL versions of a database’s FSL
access provider schema.
AccessProvider
documents have the AccessProvider type. See
Access providers.
Staged schema
You can’t delete an access provider while a database has staged schema.
If the database has no staged schema, using this method is equivalent to making an unstaged schema change. Changes are applied immediately to the database’s active schema.
Avoid concurrent schema changes
Concurrent unstaged schema changes can cause contended transactions, even if the changes affect different resources. This includes unstaged changes made using:
-
The Fauna CLI
-
The Fauna Dashboard
-
The Fauna Core HTTP API’s Schema endpoints
A schema change triggers a transaction that validates the entire database schema. To avoid errors, do one of the following instead:
-
Perform unstaged schema changes sequentially
Return value
Type | Description |
---|---|
Document doesn’t exist. See NullDoc. |
Examples
AccessProvider.byName("someIssuer")?.delete()
AccessProvider.byName("someIssuer") /* deleted */
Is this article helpful?
Tell Fauna how the article can be improved:
Visit Fauna's forums
or email docs@fauna.com
Thank you for your feedback!