-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
aws_dms_certificate doesn't import Oracle wallet correctly #13605
Comments
…o, so certificate_wallet is not encoded twice
I'm having the same issue. We can't use the I've opened a PR to try to fix this issue |
#13605 added base64decode string before sending to aws-sdk-go, so cer…
This has been released in version 3.33.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Terraform Version
v0.12.20
v0.12.16
Affected Resource(s)
aws_dms_certificate
Terraform Configuration Files
Debug Output
Output shows as successful, the DMS certificate is visible in the AWS console
Expected Behavior
The imported certificate should be valid
Actual Behavior
The imported certificate isn't valid.
Importing the certificate in the AWS console works and the below cli import is successful;
The TF state contains the correct base64 encoded certificate, but when TF imports it into AWS DMS, a second base64 encoding is applied corrupting the certificate.
Important Factoids
If I try;
It fails with 'provided string is not valid UTF-8'
There were changes to the certificate_wallet input back in version v2.46.0, but this issue occurs in versions before or after 2.46
#11496
References
The text was updated successfully, but these errors were encountered: