SecretManager: Add a wrapper to block endless calls

[ElectNewt]

SecretManager: Add a wrapper to block endless calls

[AlexScigalszky]

Maybe it's a good place to implement Memoization (I've never do that)..
Maybe something like this

public async Task<T> Get<T>(string path) 
    where T : new()
{
    VaultClient client = new VaultClient(new VaultClientSettings(_vaultSettings.VaultUrl,
        new TokenAuthMethodInfo(_vaultSettings.TokenApi)));

    var requestFn = async (string path) => await client.V1.Secrets.KeyValue.V2.ReadSecretAsync(path: path, mountPoint: "secret");

    Secret<SecretData> kv2Secret = await requestFn.ThreadSafeMemoize()(path);
    
    var returnedData = kv2Secret.Data.Data;
    return returnedData.ToObject<T>();
}

public static Func<A, R> ThreadSafeMemoize<A, R>(this Func<A, R> func)
{
    return Memoizer.ThreadSafeMemoize(func);
}

public static Func<A, R> ThreadSafeMemoize<A, R>(Func<A, R> func)
{
    var cache = new ConcurrentDictionary<A, R>();
    return argument => cache.GetOrAdd(argument, func);
}

Of course, with this approach it's impossible to implement retries and in case of an error, the error will be in the cache and it will be the result while the application is running. I don't know, it's just a good place to practice Memoization xD

[ElectNewt]

@AlexScigalszky nah memoization is good when you have to query something and then query it again and again, etc and you konw it will never change. in this case the issue is different.

the idea on this task is to intercept somehow the failed queries by unauthorrized and do the getconnection call then retry with the new credentials, being completly transparent to the app.

---

A good place for memoization is in the MongoConnectionProvider :

the GetMongoUrl can be done with memoization

Distribt/src/Shared/Shared.Databases/Distribt.Shared.Databases.MongoDb/MongoDbConnectionProvider.cs

Line 28 in af815d5

public MongoUrl GetMongoUrl()

, at least until this task is implemented