[DOCS-8019] GLOBAL OWNER and Cloud Manager Created: 03/Jun/16  Updated: 11/Jan/17  Resolved: 06/Jun/16

Status: Closed
Project: Documentation
Component/s: Cloud Manager, Ops Manager
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Task Priority: Minor - P4
Reporter: John Page Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 7 years, 36 weeks, 2 days ago

 Description   

Our docs here https://docs.cloud.mongodb.com/tutorial/create-cluster-with-api/

Give you a tutorial for Cloud Manager which requires you to have the Global Owner role.

Does this make any sense? No-one has GLOBAL_OWNER except MongoDB internal admins.



 Comments   
Comment by Andrew Davidson [ 06/Jun/16 ]

I think the example was originally written with the idea that "OK You want to deploy a sharded cluster on a fresh new Ops Manager, well here's how it can be done with the very minimum amount of UI usage, e.g. registering one global user in the UI and then up and going". But for purposes of the general documentation, this should be generalized to the Group Owner here!

Comment by David Golub [ 06/Jun/16 ]

This looks like a typo and probably should have been Group Owner, although it looks like Group User Admin and Group Automation Admin should be enough to hit all of those endpoints.

Comment by Bob Grabar [ 06/Jun/16 ]

michael.benoit, david.golub,

It appears that a user with the Owner role (i.e., a Cloud Manager Owner) can indeed perform the procedure to "Deploy a Cluster through the API" (here).

Can you confirm?

The procedure includes these endpoints:

POST /api/public/v1.0/groups
POST /api/public/v1.0/users
GET /api/public/v1.0/groups/GROUP-ID/users
DELETE /api/public/v1.0/groups/GROUP-ID/users
PUT /api/public/v1.0/groups/GROUP-ID/automationConfig

cc andrew.davidson

Generated at Thu Feb 08 07:55:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.