[DOCS-5520] API: Missing documentation/example for generation of new excluded namespace list Created: 31/May/15 Updated: 11/Jan/17 Resolved: 22/Feb/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Sommer | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 8 years, 5 days ago | ||||
| Description |
|
https://docs.mms.mongodb.com/reference/api/backup-configurations/ When updating the excluded namespaces, if submitting a list that includes that existing list + additions, supplying the excludedNamespaces field is enough. If, however, the list results in the removal of currently excluded namespaces, the syncSource field must be included as well. (This is because the removal necessitates a full resync.) Without the additional field, the API call will succeed, but the list will not change. |
| Comments |
| Comment by Michael Benoit [ 12/Feb/16 ] |
|
I think the behavior for includedNamespaces would be the opposite. So:
steve.briskin should confirm this. |