Remove the requirement to have an API Access List CIDR before being able to manage backup schedules
The issue is described in this github issue, specifically in the linked comment: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/222#issuecomment-855905952
Here is the requirement as described in the API docs: Remove All Cloud Backup Schedules
Removes all cloud backup schedules for the specified cluster. "This schedule defines when MongoDB Cloud takes scheduled snapshots and how long it stores those snapshots. To use this resource, the requesting API Key must have the Project Atlas Admin role and an entry for the project access list."
https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Cloud-Backups/operation/deleteAllBackupSchedules
Our request is that the requirement to have an API Access List to manage backup policies be removed.
At the very least, it would be good to document why this restriction is in place so folks like me hopefully stop pestering you about it.
We understand there is a workaround (adding 0.0.0.0/1 and 128.0.0.0/1 CIDR), but that feels very awkward and is unintuitive.
The behavior just doesn't match the rest of the API and is very unexpected.
It sounds like the ship has sailed on this one given the discussion in the github issue, and that's actually ok. But an explanation as to why this requirement is in place would be helpful.
I suspect this has something to do with the Backup Compliance Policy, but stating that would be very appreciated
Jeff Gandt
shared this idea
-
AdminFuat
(Admin, MongoDB)
commented
API Access list requirements will be removed for all APIs with upcoming Atlas updates in August 2023. Tentative release date is 08/02. Users can still require Access List for all API calls by enabling the enforcement in project settings.