-
Notifications
You must be signed in to change notification settings - Fork 178
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
INTMDB-206 Documentation and example updates #453
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.
Two very small suggested edits for clarify but otherwise LGTM!
@@ -15,6 +15,8 @@ The MongoDB Atlas provider offers two paths to perform an authorization for a cl | |||
* A two resource path, consisting of `mongodbatlas_cloud_provider_access_setup` and `mongodbatlas_cloud_provider_access_authorization`. The first resource, `mongodbatlas_cloud_provider_access_setup`, only generates | |||
the initial configuration (create, delete operations). The second resource, `mongodbatlas_cloud_provider_access_authorization`, helps to perform the authorization using the role_id of the first resource. This path is helpful in a multi-provider Terraform file, and allows a single and decoupled apply. | |||
|
|||
-> **IMPORTANT** If it is needed to migrate from the single resource to the two resource paths see the [migration guide](https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/guides/0.9.1-upgrade-guide#migration-to-cloud-provider-access-setup) |
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 would edit this slightly to:
If you want to move from the single resource path to the two resources path see the migration guide
@@ -57,6 +57,15 @@ resource "mongodbatlas_encryption_at_rest" "test" { | |||
} | |||
``` | |||
|
|||
**NOTE** in case using the `cloud_provider_access_setup` and `cloud_provider_access_authorization`, could be a use case where it needs to define the `depends_on` statement for these two resources, because terraform is not able to infer. |
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.
Suggested edit that may help clarify:
NOTE if using the two resources path for cloud provider access, cloud_provider_access_setup
and cloud_provider_access_authorization
, you may need to to define a depends_on
statement for these two resources because terraform is not able to infer the dependency.
variable "atlas_region" { | ||
default = "US_EAST_1" | ||
description = "Atlas Region" | ||
} |
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.
same GH linter error as before
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
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, thank you!
Description
Updating the documentation guide for migration for the cloud_provider_access_setup and adding one example to using it with the encryption_at_rest for aws.
Link to any related issue(s):
#451
#409
Type of change:
Required Checklist:
Further comments