[DOCS-16183] Atlas Admin API doc correction Created: 26/May/23  Updated: 16/Jun/23  Resolved: 16/Jun/23

Status: Closed
Project: Documentation
Component/s: API, Atlas
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Will Huang Assignee: Evelyn Rabil
Resolution: Done Votes: 0
Labels: cet-captain, highlight-for-planning
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Participants:
Days since reply: 35 weeks, 5 days ago

 Description   

Hi Docs team,

The Monitoring and Logs section of the Atlas Admin API states that To use this resource, the requesting API Key must have the Project Owner or Project Data Access Read/Write roles. This resource doesn't require the API Key to have an Access List. However, I and a customer who has our API key was granted the role of Project Data Access Read Only and were still able to use this API resource. Can someone confirm if this should be restricted to Project Owner and Project Data Access Read/Write roles only? If not, I believe the doc should be updated. Ty.



 Comments   
Comment by Vincent Do [ 02/Jun/23 ]

I believe this is just a confusion in terminology. The access written in the code is read OR write and so the user can use either the read only or the read_write role.

Comment by Yuta Arai [ 31/May/23 ]

Atlas HELP Rotation Bug Triage Notes
This bug has been triaged to your team based on the distribution of bugs across Atlas (Atlas Bug Board)

Generated at Thu Feb 08 08:14:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.