Skip to content

Draft: enabling vm cache for elasticsearchcred

Akanksha Prasad requested to merge akprasad/elasticsearch-cred into azure/m16-master

Type of change

  • [yes] Bug Fix
  • [no] 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?

  • [YES] Azure

Does this introduce a breaking change?

  • [NO]

What is the current behavior?

ElasticSearch Cred is fetched from redis cache which was causing during update of elastic search primary user secret as 500 ,internal server error.This was majorly because,refresh time of redis is 60 minutes.Hence,in that duration 500 status code was returned

What is the new/expected behavior?

After the duration of secret rotation completed,search should return 200 success status code

Have you added/updated Unit Tests and Integration Tests?

yes

Any other useful information

Merge request reports