Allow disabling resilience for Ollama

[dealloc]

Related to an existing integration?

Yes

Existing integration

CommunityToolkit.Aspire.OllamaSharp

Overview

When making calls to Ollama using extended thinking or larger prompts, the chance a single request will take longer than 10s which will trigger Aspire's default resilience handlers.

for example:

routes.MapGet("/", static ([FromKeyedServices("thinking")] IChatClient client) => Results.ServerSentEvents(
	client
		.GetStreamingResponseAsync([new ChatMessage(ChatRole.User, "Hello, world!")])
		.Where(message => string.IsNullOrWhiteSpace(message.Text) is false)
		.Select(message => message.Text),
	eventType: "message"
));

Usage example

Ollama's AddKeyedOllamaApiClient internally registers a http client, but doesn't expose any way to configure it.

Similar to #1084 I'd like a way to access the HTTP client that's being configured internally.
Perhaps an optional argument can be added at the end of the signature?

Breaking change?

No

Alternatives

The http client is named internally as $"{connectionName}_httpClient" so I can get to it that way, but I don't like relying on internals of the integration.

Additional context

No response

Help us help you

Yes, I'd like to be assigned to work on this item

[aaronpowell]

I don't think this is something that should be exposed from the API for configuring OllamaSharp, but instead it should be done using the http resilience pipeline in .NET

[dealloc]

But for that I need the builder, do I just rely on $"{connectionName}_httpClient"?
reason I opend the issue is because it feels clunky to have a magic string in the setup that is hidden away in an extension method somewhere

[afscrome]

For your app, this was probably added by the scaffolded ServiceDefaults library. If this behaviour doesn't match your needs, you can remove and/or tune it: https://github.com/dotnet/aspire/blob/d533eea6cf6e10d77eeefbbebef6068cdf731749/playground/orleans/OrleansServiceDefaults/Extensions.cs#L28

[dealloc]

I know where and how it's added, I just wanted to be able to configure it speficially for the Ollama client.

I'm currently using this to work around this:

		// Ollama internally creates a HttpClient, but Aspire automatically attaches a 10s timeout to it.
		// The code below removes all resilience handlers (so we can override them), and then attaches
		// The same handlers with our custom configuration.
#pragma warning disable EXTEXP0001
		builder.Services.AddHttpClient($"{connectionName}_httpClient")
			.RemoveAllResilienceHandlers()
#pragma warning restore EXTEXP0001
			.AddStandardResilienceHandler(options =>
			{
				options.TotalRequestTimeout.Timeout = TimeSpan.FromDays(1);
				options.AttemptTimeout.Timeout = TimeSpan.FromHours(1);
				options.CircuitBreaker.SamplingDuration = TimeSpan.FromHours(2);
			});

I'm just not a fan of having to rely on $"{connectionName}_httpClient" as in my eyes it's an internal implementation detail of the Aspire integration, something I would have to dive into the code for