-
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
Docs: fix custom_dns_configuration_cluster_aws #860
Conversation
The import of this resource should performed using the project ID, not the auditing ID.
@tooooots thank you for the submission and for signing the CLA. Are you sure the import was successful? Can you see the resource in your state? I ask because checking the code: https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/mongodbatlas/resource_mongodbatlas_custom_dns_configuration_cluster_aws.go I don't actually see an import function. |
I just tested using provider
|
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, just added another commit updating link to our latest OpenAPI Documentation (which also highlights that Project ID is a required field for this endpoint). @martinstibbe can you double check this as well?
LGTM I also verified the CLA is signed |
Thanks @gssbzn! appreciate the double check here |
Description
The import of this resource should performed using the project ID, not the auditing ID. I think the reference to the "Auditing ID" is a typo and I've been able to import this resource using the project ID (Group ID).
References:
https://www.mongodb.com/docs/atlas/reference/api/aws-custom-dns-get/
https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/custom_dns_configuration_cluster_aws
Link to any related issue(s):
N/A
Type of change:
Required Checklist:
Further comments