[RHCLOUD-36096] Document TLS enabled if inMemoryDb.password is returned #1126
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.
JIRA issue
https://issues.redhat.com/browse/RHCLOUD-36096
Background
Notifications is loading its ElastiCache configuration via Clowder (see RedHatInsights/clowder-quarkus-config-source#291). We plan to use in-transit encryption (TLS), which requires a URI scheme of
rediss://
. However, we cannot use TLS for our test suite, and it'simpossiblevery difficult to find a way to consistently rewrite the URL.The easiest fix is to have the ConfigSource set the correct scheme when it knows TLS is being used. After reviewing Elasticache documentation, the qontract-reconcile code, and internal documentation, it's clear that
db.auth_token
can only be generated and provided when in-transit encryption is enabled. While the reverse is not necessarily true, this is enough for our purposes.Description
Add a comment to the ElastiCache provider, and update the In-Memory DB docs, to publicly confirm that if the
.inMemoryDb.password
field incdappconfig.json
, then it is known that in-transit encryption is enabled.