Skip to content

Rock

My feedback

1 result found

  1. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Atlas » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Rock commented  · 

    According to the GitHub Meta API, there are currently 5,116 IP addresses under the "actions" key. Adding all these IP addresses manually to the Atlas IP Access List would be quite cumbersome (I can do it programmatically), and I am concerned that having this many IPs in the whitelist might cause performance issues or impact the cluster's responsiveness.

    Unfortunately there is a limitation as well that will not allow over 200 ips, maybe because of my previous concern on the negative impact it might have. The work around of opening it up to everything doesn't seem reasonable either. (0.0.0.0 allow list)

    I've been a contractor for a few companies where github actions were in use and they were early on with Atlas. I wonder if they don't find a need / want for this later or have at sometime. My current job definitely has a need as we are a small team and need to automate as much as we can (small team or not this is the same practice everywhere - "automate all the things!" )

    I would not of found this to comment on without the mongo support staff pointing me in the proper direction. I get that large ip lists might be a low priority in an overall product, but maybe looking at these larger companies as services and opening access to the services, especially as things get more automated and agent based.

    Rock supported this idea  · 

Feedback and Knowledge Base