fix: SQS queue encryption types selection #2575
Merged
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.
Description
sqs_managed_sse_enabled
andkms_master_key_id
cannot coexist. prior to this fix, ifqueue_managed_sse_enabled
was set tofalse
, thensqs_managed_sse_enabled
would be set to false as well, insteadnull
, as it should be in this case.Motivation and Context
I have tried to change an SQS queue's encryption from "SSE-SQS" to "SSE-KMS", using the karpenter submodule and failed with an error saying "sqs_managed_sse_enabled": conflicts with "kms_master_key_id".
This fixes the issue.
Breaking Changes
None known.
How Has This Been Tested?
I have successfully deployed with this change in my environment, where SQS queues are managed by the karpenter submodule for about 2 months now.
I have executed
pre-commit run -a
on my pull request