accessProvider.update()
| Learn: Access providers |
|---|
|
We recommend you use FSL to create and update access providers. See FSL access provider schema. |
Updates an access provider.
Description
The update() method updates the provider with the object fields
and returns the updated provider. During the update, fields from object
are copied to the document, creating new fields or updating existing
fields. The operation is similar to a merge.
Only the fields included in object are updated, all other document fields aren’t updated. Fields with nested objects in object are merged with the identically named nested object in the document.
To remove a document field, set its value in object to null.
Considerations
If a database has staged schema, this method interacts with the database’s staged schema, not the active schema.
You can’t rename 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:
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
Examples
AccessProvider.byName("someIssuer")?.update({
name: "someIssuer",
issuer: "https://example.com/",
roles: "customer"
}){
name: "someIssuer",
coll: AccessProvider,
ts: Time("2099-06-25T15:00:27.295Z"),
jwks_uri: "https://example.com/.well-known/jwks.json",
roles: "customer",
issuer: "https://example.com/",
audience: "https://db.fauna.com/db/ysjowue14yyr1"
}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!