Skip to content

Atlas

← MongoDB Feedback Engine
Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

How can we improve the platform?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

1 result found

  1. Vault should return users only once they can be used

    Currently, the Vault Plugin immediately returns the MongoDB users after they are created in Atlas. However, they have not been rolled out to the actual nodes yet. Immediately using them on a cluster will fail.

    Unfortunately MongoDB does not want to provide a fixed maximum time to wait, as the time apparently depends on many factors, including how many clusters are in a project, or if there are other changes being rolled out.

    It would be a much simpler and better user experience if the Vault plugin would only return the user once it is actually usable, even if that…

    7 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Vault Plugin  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    declined  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    Hi all,  


    This request was first made via a Vault repo issue: https://github.com/hashicorp/vault-plugin-database-mongodbatlas/issues/10  We investigated the options with the Vault engineering team and the conclusion, from the issue is:


    "We have researched the options to address this feature request and  discussed it with the Vault engineering team.  After this it became apparent that there is no safe and solid way to do this and it would be  better to continue to function as most secrete engines do, which results  in an eventually consistent experience in regard to secret creation.   I  encourage those who need to know when the database credential is fully  available to use the status endpoint mentioned earlier in this issue, https://docs.atlas.mongodb.com/reference/api/clusters-check-operation-status/)."


    Thank you,

    Melissa


  • Don't see your idea?

Atlas

Categories

Feedback and Knowledge Base

(thinking…)