Allow Use of IConfigureOptions Consistently Everywhere

Is your feature request related to a problem? Please describe.

IConfigureOptions<T> allows you to move your configuration code to a separate class. However, it cannot be used with certain API’s which require us to pass an Action<T>:

IServiceCollection AddStackExchangeRedisCache(this IServiceCollection services, Action<RedisCacheOptions> setupAction)
IServiceCollection AddHsts(this IServiceCollection services, Action<HstsOptions> configureOptions)

This is not an exhaustive list, there may be others.

Describe the solution you’d like

All API’s in ASP.NET Core should be consistent and allow us to configure them using IConfigureOptions<T>. The following overloads should be added:

IServiceCollection AddStackExchangeRedisCache(this IServiceCollection services)
IServiceCollection AddHsts(this IServiceCollection services)

[pranavkm]

API review:

• Don’t change existing overloads.
• For existing APIs that are missing the overload that does not accept an options callback, we should add one. For e.g we should do this:

+ IServiceCollection AddStackExchangeRedisCache(this IServiceCollection services)
IServiceCollection AddStackExchangeRedisCache(this IServiceCollection services, Action<RedisCacheOptions> setupAction)

• For new ones, we think standardize on using the pattern of having two overloads. This should allow for new options to be introduced in a future release without deviating from the pattern and also conforms to existing patterns in the framework.

public static IServerSideBlazorBuilder AddMyFeature(this IServiceCollection services);
public static IServerSideBlazorBuilder AddMyFeature(this IServiceCollection services, Action<MyFeatureOption> configureOptions) ;

configureOptions in the above example can be allowed to be soft-allow null values (i.e. not perform null checks) for the sake of brevity of implementation.

• In the event we only need the options type to configured without adding any other services, we should standardize on Configure??? as the name for the method e.g. ConfigureMyFeatureOptions(Action<MyFeatureOptions> configureOptions) where configureOptions is non-null.

Separately we’ll approve the changes proposed in this issue:

+ IServiceCollection AddStackExchangeRedisCache(this IServiceCollection services)
+ IServiceCollection AddHsts(this IServiceCollection services)

[halter73]

API Review Notes:

Options can be configured separately without the callback, but this is uncommon. We’re worried that introducing this overload will create confusion only to save seven characters of code in the uncommon case.

We are worried that adding the non-options-configuring AddStackExchangeRedisCache(this IServiceCollection services) will create too much confusion by making people think configuring options isn’t necessary. If options are configured seperately, calling AddStackExchangeRedisCache(this IServiceCollection services, Action<RedisCacheOptions> configure) with _ => { } is easy enough.