feat: Add support for service connect tls settings #216
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
Adds support for
tls
underservice_connect_configuration.service
. Withintls
, you can specifyissuer_cert_authority
,kms_key
androle_arn
. Those fields are documented here.Motivation and Context
This change allows the user to enable TLS and encrypt Service Connect traffic. The default settings are not adequate for all use cases.
Breaking Changes
None
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull requestNo examples were appended due to the nature of the TLS configuration requiring an AWS Certificate Manager Private Certificate Authority. If you feel this should be implemented in one of the examples anyway, let me know.