Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added documentation for mongodb atlas database secrets engine eventua… #24152

Merged
merged 5 commits into from
May 1, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions changelog/24152.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
```release-note:improvement
website/docs: Add note about eventual consietency with the MongoDB Atlas database secrets engine
```
10 changes: 10 additions & 0 deletions website/content/docs/secrets/databases/mongodbatlas.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,16 @@ the proper permissions, it can generate credentials.
username v-my-password-role-DKbQEg6uRn
```

Each invocation of the command generates a new credential.

MongoDB Atlas database credentials eventually become consistent when the
[MongoDB Atlas Admin API](https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/)
coordinates with hosted clusters in your Atlas project. You cannot use the
credentials successfully until the consistency process completes.

If you plan to use MongoDB Atlas credentials in a pipeline, you may need to add
a time delay or secondary process to account for the time required to establish consistency.

#### Client certificate credentials

1. Configure a role that maps a name in Vault to a MongoDB Atlas command that executes and
Expand Down
Loading