Description

The stress project has a bunch of APIs for causing certain behavior. For example, /log-message logs a message with a bunch of unusual content. This PR adds commands to call the APIs from the dashboard.

@DamianEdwards Some issues I encountered using WithHttpCommand:

• Order matters. If commands are added before endpoints then it errors. A fix could be to resolve the endpoint inside the command callback.
• Command name is based on the method. If there are lots of "GET" commands then they're reduced to one. Need a better automatic name (I modified the method to include the URL in the name)
• Needs HttpClientFactory registered. It's not registered in app host by default. Bug or not? An improvement could be to detect if it is registered or not and throw a more friendly error message.

Screenshot:

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
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue:
  • No

Microsoft Reviewers: Open in CodeFlow