added azure authorization implementation with a cache
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [NO]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
Google Cloud -
IBM
Does this introduce a breaking change?
- [NO]
What is the current behavior?
Entitlements request for the API authorization is never cached and so goes to entitlements service everytime
What is the new/expected behavior?
For a response to be cached in Redis and used when available
Have you added/updated Unit Tests and Integration Tests?
Unit tests added