[release/13.5] Mark Radius provider builders experimental

Merged
SE
1mo ago
+8-0

Description

Marks the Radius AWS and Azure cloud-provider callback interfaces with Experimental("ASPIRERADIUS003"), matching the WithAwsProvider and WithAzureProvider methods that expose them. This keeps consumers from referencing the callback contracts without acknowledging the same experimental stability boundary.

The internal provider builder implementations carry the same attribute so their implementation of the experimental contracts compiles without broad warning suppression.

This addresses the issue identified in the review of #19866: https://github.com/microsoft/aspire/pull/19866#discussion_r3916992948. Generated API baseline files are intentionally unchanged here; #19866 regenerates and pins the release surface separately.

Validation: all 207 tests in Aspire.Hosting.Radius.Tests pass.

Fixes # (issue)

Checklist

  • Is this feature complete?
    • Yes. Ready to ship.
    • No. Follow-up changes expected.
  • Are you including unit tests for the changes and scenario tests if relevant?
    • Yes
    • No
  • Did you add public API?
    • Yes
      • If yes, did you have an API Review for it?
        • Yes
        • No
      • Did you add <remarks /> and <code /> elements on your triple slash comments?
        • Yes
        • No
    • No
  • Does the change make any security assumptions or guarantees?
    • Yes
      • If yes, have you done a threat model and had a security review?
        • Yes
        • No
    • No