-
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
Enabling encryption at rest with any provider for a Cluster will throw error #517
Comments
Already reported internally, issue known and will be fixed by internal ticket INTMDB-243. Expect in 1.0.1 bug fix release. |
@themantissa any ETA on the 1.0.1 release ? |
@nleite we are working to get this out ASAP so hopefully quite soon. |
just to raise an awareness - we are also affected by the same bug on AWS. |
We have a pre-release of 1.0.1 ready - we'll release the GA version tomorrow. If you have time to try it out before then it's here: https://github.com/mongodb/terraform-provider-mongodbatlas/releases/tag/v1.0.1-pre.1 |
Fixed in recent release 1.0.1 |
Terraform CLI and Terraform MongoDB Atlas Provider Version
Terraform Configuration File
The above assumes Azure Key Vault is already created and Encryption at Rest is already configured at the project-level in Atlas. Happy to share the full script which creates these resources as well if relevant.
Steps to Reproduce
terraform init
terraform apply
Expected Behavior
Should have applied the plan successfully. The same TF script works without any issues on 0.8.2 and 0.9.1.
Actual Behavior
Terraform throws an error when setting encryption at rest for the cluster:
I have tried switching to the new syntax (azure_key_vault_config instead of azure_key_vault) but this let to the same outcome. Since this error didn't occur with the exact same TF scripts on previous versions, I highly suspect it's a bug with the provider.
Additional Context
I have tried the new style config:
But it also fails with the old style config:
Oddly enough, the error isn't thrown until it actually starts applying the changes. Syntax errors (if this would be a syntax error like the error implies) are usually thrown at start when reading the script to create the plan. Additionally, after this error is thrown it doesn't allow me to run
terraform destroy
to 'revert' the changes as it throws the same error again and aborts.The text was updated successfully, but these errors were encountered: