docs/resource/aws_msk_cluster: Additional information about bootstrap_brokers and bootstrap_brokers_tls #8957
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
…_brokers and bootstrap_brokers_tls Reference: #8952 Specifying only TLS encryption in transit for client-broker communication was a recent feature addition. Here we update the example and attribute references to account for the cases where the values should be filled in depending on that encryption in transit setting.
bflad
added
documentation
|
@bflad maybe some mention of which is the default? |
|
The existing |
|
Rebased against master. |
|
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! |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Community Note
Closes #8952
Specifying only TLS encryption in transit for client-broker communication was a recent feature addition. Here we update the example and attribute references to account for the cases where the values should be filled in depending on that encryption in transit setting.
Release note for CHANGELOG:
Output from acceptance testing: N/A documentation update