-
Notifications
You must be signed in to change notification settings - Fork 170
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
fix: support update of description for project api key resource #1354
Conversation
…ation and fixing role_names attribute in project assignments
The following are valid roles: | ||
* `GROUP_OWNER` | ||
* `GROUP_READ_ONLY` | ||
* `GROUP_DATA_ACCESS_ADMIN` | ||
* `GROUP_DATA_ACCESS_READ_WRITE` | ||
* `GROUP_DATA_ACCESS_READ_ONLY` | ||
* `GROUP_CLUSTER_MANAGER` | ||
* | ||
### Programmatic API Keys |
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.
This section is unrelated to project api key resource, seems like a copy paste that came from project resource documentation
Project Assignment attribute is optional (Use project_assignment going forward as role_names parameter above is deprecated) | ||
|
||
* `project_id` - (Required) Project ID to assign to Access Key | ||
* `role_names` - Name of the role. This resource returns all the roles the user has in Atlas. | ||
* `role_names` - (Required) List of Project roles that the Programmatic API key needs to have. Ensure you provide: at least one role and ensure all roles are valid for the Project. You must specify an array even if you are only associating a single role with the Programmatic API key. |
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.
role_names is marked as required in our schema, and also verified that an empty array causes project assignment to not be created.
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. My comments are not blocking the PR. Great work!
Hello @pierwill @zach-carr @jwilliams-mongo! I will be merging this PR, but feel free to review and if you have any comments I can address them in a separate PR. |
Description
Ticket: INTMDB-917
Updating description of an api key in the mongodbatlas_project_api_key resource was not contemplated in update. This includes a new request for handling this scenario.
Type of change:
Required Checklist:
Further comments