-
Notifications
You must be signed in to change notification settings - Fork 190
Add Organisation and Project invitations #560
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution, I have made an initial pass of the PR mostly some small style recommendations, I mostly singled out a line but some of the recommendations apply to multiple cases
Also a this is a big blocker, it seems this PR is lacking some unit testing at least, once those are done we can take another look
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's looking good but I left some suggestions related to validation
mongodbatlas/data_source_mongodbatlas_project_invitation_test.go
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for all the work here 💯 and thanks for adding those tests, I left a couple of comments on things that we could simplify also not reviewing docs, delegating that to @themantissa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
almost there, some places were you were doing replace instead of join are still missing, also thanks for removing the dependency on log
but the linter is reporting you still import it so we should fix that, other than that LGTM from me
Thanks @gssbzn I ran out of time last night. I will get this done on Monday morning Oz time. |
Well I guess I found time when having breakfast :-) |
@beergeek I will review the docs soon. FYI this will not go in our next release (1.0.2) but in 1.1.0 since it's a major feature add. Let me know if any questions on this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks for all the work here 💯
@coderGo93 I just re-requested your review as you had requested changes that @beergeek has made. Can you take a look and confirm and approve please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some comments related to schema of roles
in datasource(s)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly docs comments but one on the omission of teams for org. Bad copy/paste comments all a bit jokey but please do check we don't have any of these entries from db user ;) Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM if the tests passes, thanks for the changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking really good - just a few more nits in the docs. I'll also have one of our doc team members taking a look as they will be able to start helping us with the documentation PRs!
## Argument Reference | ||
|
||
* `org_id` - (Required) The unique ID for the project to create the database user. | ||
* `username` - (Required) The Atlas user's email address. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still think it wouldn't hurt to clarify this more but am happy to hear any reason why we should not do so.
resource "mongodbatlas_org_invitation" "test" { | ||
username = "test-acc-username" | ||
org_id = "<ORG-ID>" | ||
roles = [ "GROUP_DATA_ACCESS_READ_WRITE" ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still a project role in example.
@jwilliams-mongo first review of a PR containing docs. If you have any questions let me know. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some suggestions for clarity, for grammar, and to bring the documentation more in line with the Atlas API documentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for all the work on this! LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM % suggestions in two resolved comments that don't appear to have made it in to the PR.
* Add Organisation and Project invitations * Fix linting issues * Change to American spelling * Apply fixes and suggested modifications * Fix the linting issues * Fix the linting issues * Add tests * Refactor portions of the code to reduce the amount of code required * Changes as requested * Changes as requested * Changes to code as requested, plus doc updates * Fix conflict * Fix context and spelling * Fix spelling and grammar as advised * Further spelling and grammatical fixes * refactor: fixed many bugs that couldn't be tested locally Co-authored-by: beergeek <[email protected]> Co-authored-by: Melissa Plunkett <[email protected]> Co-authored-by: Edgar López <[email protected]>
Description
This update provides both resource and data source for invitations at the Organisation and Project levels.
Link to any related issue(s):
Type of change:
Required Checklist:
Further comments