Does Aspire support enabling HTTP/2?

[Allen0117]

I recently discovered that WireMock.NET supports Aspire, and I’ve started using it successfully. However, in real products we inevitably encounter gRPC, so naturally I wanted to use WireMock.NET with Aspire to mock gRPC as well. Unfortunately, I couldn’t find any related documentation, and after tracing through the code, I also noticed that none of the external customization parameters seem to support this.

So I’d like to ask: is this something that’s simply not planned to be supported, or will it be supported in the future?

[StefH]

@Allen0117
I think that exposing UseHttp2 in WireMockServerArguments should work?

[StefH]

#1383

[Allen0117]

I think placing UseHttp2 under WireMockServerArguments does make gRPC work properly. As for AddProtoDefinition, would you prefer it to use the mapper’s given configuration? Or how would you like it to be used within Aspire?

[StefH]

You can try preview
1.16.0-ci-110628

https://wiremock.org/dotnet/myget-preview-versions/

[Allen0117]

Hi @StefH I’d like to understand the issue regarding the gRPC port. In TestContainer, I can use AddUrl("grpc://*:9090"), but I’m not sure how to define this in Aspire.

[StefH]

Can you try
1.16.0-ci-110634

This one has a constructor
.AddWireMock("apiservice", ["http://:8080", "grpc://:9090"])

[StefH]

@Allen0117
Could you test it?

[Allen0117]

Sorry @StefH I’m currently validating it in parallel with WireMockTestContainer, and I hope the approaches used on both sides can be as similar as possible.
Do you have a pending time on your side? If so, I can focus on WireMockAspire first.

[StefH]

Testcontainers did already support https grpc.
See also my unit tests.

So I think you can focus on Aspire.

[Allen0117]

I’ve already verified that the Testcontainers case works without issues.
I simply want to see whether the same approach can also be used in Aspire, and as mentioned earlier, I hope the usage patterns can be as similar as possible.
For now, I’ll focus on the Aspire part first.

Additionally, I noticed that when Testcontainers uses WithMapping or WithMount for JSON files, they are correctly placed under /app/__admin/mappings, but validation still results in errors. I also saw that others have reported the same issue in the past (e.g., GitHub issue #1274). I’m not sure if this is the expected behavior?

[StefH]

For now, I’ll focus on the Aspire part first.

Thanks a lot. If you can test this and it works I can merge the PR and create a new version.

---

Additionally, I noticed that when Testcontainers uses WithMapping or WithMount for JSON files, they are correctly placed under /app/__admin/mappings, but validation still results in errors. I also saw that others have reported the same issue in the past (e.g., GitHub issue #1274). I’m not sure if this is the expected behavior?

I need to find time to investigate this in more detail...