Client side changes for open search support

chef / automate

Chef Automate provides a full suite of enterprise capabilities for maintaining continuous visibility into application, infrastructure, and security automation.

https://automate.chef.io/

Apache License 2.0

225 stars 113 forks source link

Client side changes for open search support #6583

Open punitmundra opened 2 years ago

punitmundra commented 2 years ago

This Story is about

Change the Client side code in Automate refer below PR : https://github.com/chef/automate/pull/4435/files https://github.com/chef/automate/pull/4293/files
Set up the Open-search Manually OR used the managed Open-search(by AWS).
Change the client side Library in Automate
Deploy new code changes with External Open-search via config.toml, it should start working.

Acceptance Criteria

Automate code should compile
Able to make connection with open search
Able to write and read the data via automate service
Able to query data from automate UI,

Note: This might require Current ES-6.8 may be out of the bundle (Not sure on that).

jayvikramsharma1 commented 2 years ago

Code is migrated, fixed the build for all required services, now all build is sucessfull

jayvikramsharma1 commented 2 years ago

PR link, it is just for reference, not ready for merge yet, Testing in pending, https://github.com/chef/automate/pull/6607/files

jayvikramsharma1 commented 2 years ago

fixed all issue in starting services, and communication with opensearch is working, fixed upfront coming mapping issue, we need to test further.

jayvikramsharma1 commented 2 years ago

We are validating Automate UI for any api failure or Ui breaking, few apis are breaking in prod env, but in local env it works fine no error, also in log not getting detailed error message, we are just getting shard failure, we need to debug failure for root cause in order to fix the issue.