Make AddAWSDynamoDBDistributedCache *only* add and not configure as well

[rb1n]

The current approach is not ideal when you want to add the services separately to configuring them.

eg it would be useful to be able to configure in one place:

services
    .AddOptions<DynamoDBDistributedCacheOptions>()
    .Configure<IConfiguration>((options, config) => config.GetSection("DynamoDBCache").Bind(options))
    .ValidateDataAnnotations();

// other configuring...

then be able to add the services somewhere else, allowing DI to resolve the options

services.AddAWSDynamoDBDistributedCache();

// add other services...

[ashishdhingra]

@rb1n Good morning. Thanks for opening the issue. Looks like you are referring to OptionsBuilder API and comparing the implementation to MemoryCacheServiceCollectionExtensions.AddDistributedMemoryCache. For AddDistributedMemoryCache(IServiceCollection), the dependency would be resolved here, where services.AddDistributedMemoryCache() adds singleton instance of MemoryDistributedCache.

I will review this feature request with the team.

Thanks,
Ashish

[ashishdhingra]

@rb1n Good morning. This is a valid feature request based on review with the team.

Following pattern used for MemoryCacheServiceCollectionExtensions.AddDistributedMemoryCache, feel free to contribute PR, if possible. Perhaps we should:

• Add support for adding DynamoDBDistributedCacheOptions on services.AddOption<T>.
• Add overload of services.AddAWSDynamoDBDistributedCache() which tries to resolve the options added earlier. May be it will use default options or throw exception if no options were configured earlier (we could decide the implementation).