fix: add support postgres existingSecret for indexer #82
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.
PR(Pull Request) Overview
This PR adds support for indexer authentication to postgres database when using existingSecret instead of plain text password.
Changes
Description of Changes
When we use postgres sub chart as dabase for indexer and use plain text password every time we update the helm chart config the postgresql sub-chart create a new secret and postgresql will be restarted, to prevent postgresql from restarting we should use existingSecret in the auth section of postgres config, this PR supports using the existing secret for indexer service.
Testing Method
Explain how to test the changes step by step: