Setting ca_cert_identifier default value to null #115
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ion up to the rds resource
|
/test all |
|
@nnsense thanks for the contribution as always -- it seems our got stuck which is an annoying occurrence. Mind doing the following to bump that? |
|
Hi @Gowiem is there anything else I should do? |
|
/test all |
Gowiem
approved these changes
Jun 14, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
what
Setting ca_cert_identifier default value to null, leaving its resolution up to the AWS resource.
why
Creating RDS in newer regions such as
eu-south-1,ap-east-1,me-south-1,af-south-1errors but RDS instance is still created. The default CA certificate ID (rds-ca-2019), which is valid across most of the regions, has a different format on these, see: #114 (comment)references
closes #114