Doc update on how to add resolvers for PG and ES gateways #4502
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.
Signed-off-by: Kallol Roy karoy@progress.com
🔩 Description: What code changed, and why?
The PR here #4486 allows automate to now resolve the Postgres cluster and Elasticsearch nodes using resolvers. The resolvers can be set in the
config.toml
by the users.The changes document how to configure resolvers in case of external PG or ES.
⛓️ Related Resources
Updated install.md file to add sections:
👍 Definition of Done
The document should have the sections mentioned above with the details of the configuration.
👟 How to Build and Test the Change
make serve
✅ Checklist
📷 Screenshots, if applicable