feat(core): Make cache configuration configurable at runtime

[tusharxoxoxo]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

#3276

How did you test it?

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible
• I added a CHANGELOG entry if applicable

[tusharxoxoxo]

1. I think I should also change the values in crates/storage_impl/src/reddis/cache.rs but it is throwing an error whenever I try to change it, can someone guide me on how this could be done

2. My LSP is showing this error, even when I haven't made any changes to the code base
   

[tusharxoxoxo]

@dracarys18

[dracarys18]

Can you run

cargo c 

and check the error

[dracarys18]

Regarding change this in cache.rs, since this is a static we can't make it completely runtime configurable. Instead you can make consts like MAX_CAPACITY a static, You can refer

hyperswitch/crates/external_services/src/kms.rs

Line 22 in 5ad3f89

KMS_CLIENT.get_or_init(|| KmsClient::new(config)).await

. This is ideally how we should do it

[tusharxoxoxo]

by doing cargo c, I do not see any error

[tusharxoxoxo]

I will change my PR according to the way u mentioned above

[tusharxoxoxo]

in issue #3276, max_capacity was taken u32 but when it's used in crates/storage_impl/src/reddis/cache.rs it is u64, should I leave it as it is or make changes to it, either make both of them u64?

const MAX_CAPACITY: u64 = 30;
is already declared static in cache.rs at the top

[dracarys18]

in issue #3276, max_capacity was taken u32 but when it's used in crates/storage_impl/src/reddis/cache.rs it is u64, should I leave it as it is or make changes to it, either make both of them u64?

const MAX_CAPACITY: u64 = 30; is already declared static in cache.rs at the top

You can keep it u64 as moka internally want you to pass this type in max_capacity