Support for self-signed certificates for ElasticSearch connection(GONRG-776, GONRG-539)
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [YES]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- [YES]
What is the current behavior?
Indexer does not support for self-signed certificates for ElasticSearch connection
What is the new/expected behavior?
To use self-signed certificates for Elastic on non-production environments.
Have you added/updated Unit Tests and Integration Tests?
Any other useful information
GCP Unify logic for credentials (GONRG-539)
Description:
- Moved credentials classes into core-lib-gcp.
How to test:
Business test cases.
Changes include:
-
Refactor (a non-breaking change that improves code maintainability). -
Bugfix (a non-breaking change that solves an issue). -
New feature (a non-breaking change that adds functionality). -
Breaking change (a change that is not backward-compatible and/or changes current functionality).
Changes in:
-
GCP -
Azure -
AWS -
IBM
Dev Checklist:
-
Added Unit Tests, wherever applicable. -
Updated the Readme, if applicable. -
Existing Tests pass -
Verified functionality locally -
Self Reviewed my code for formatting and complex business logic.
Other comments:
Any comments to approvers here
Edited by Riabokon Stanislav(EPAM)[GCP]