-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
#13605 added base64decode string before sending to aws-sdk-go, so cer… #17958
Conversation
…o, so certificate_wallet is not encoded twice
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.
Hi @sonikro , thank you for creating this PR! the resource change looks like what we need 👍 To get this into the upcoming release, I'm going to push up additional logic to handle encoding the value back on read, else a non-empty plan will result after applying a config with the certificate_wallet
argument. In addition, i've taken the opportunity to refactor some bits since there still exists quite some legacy logic.
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.
Thanks again @sonikro 🚀
Output of acceptance tests (commercial):
--- PASS: TestAccAWSDmsCertificate_disappears (10.21s)
--- PASS: TestAccAWSDmsCertificate_CertificateWallet (13.87s)
--- PASS: TestAccAWSDmsCertificate_basic (13.89s)
--- PASS: TestAccAWSDmsCertificate_tags (31.37s)
Awesome @anGie44 ! Thanks for improving the code. This is my first time using Go Lang haha. Excited for the next release, so I can finally remove my "work around" code. |
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
Closes #13605
Relates #15945
Relates #13826
When uploading Oracle Wallet files to
aws_dms_certificate
, we cant use thefile
function when reading the certificate file, because the certificate file contains invalid UTF-8 Characters. So we have to usefilebase64
function to load the certificate.Example:
However, the aws-sdk-go, already encodes the bytearray to base64, when uploading the content to AWS. So if we don't decode the base64 string, before sending to the aws-sdk-go, the aws-sdk-go will encode the content's again, causing the certificate file to be corrupted.