Nice presentation -- great structure and your code demonstration was clear!

I'm curious about your process for creating strongly-typed wrappers around the dotnet commands. Was this a manual process or did you eventually figure out a way to automate it?

Thanks so much for contributing this and updating the sample! 🫶🏾

What powerful being is lurking in the shadows there?

Should be fixed now!

Yeah the name alone is worth using it

Hurl has its own file format that’s distinct from .http files in that it lets you write assertions on the response in the file. I haven’t seen other tools that do that and have a fast and easy to use CLI experience.

My main thought here is whether or not there is ever a case where the document name doesn’t appear in the pattern in some way. Specifically because you’d want whoever is querying for the document to query based on some well-known name that appears in the URL.

Does your URL nomenclature match your document names in any way? The MapOpenApi takes a path parameter that lets you define the route for your requests so you could do something like “/{documentName}/openapi.json” of that matches why you expect.

...by declaring their own pipeline steps in the resource model using the Aspire APIs for it.

Moreso the later. The pipeline is modeled as a set of steps that are in the applicaiton model. Aspire comes with built-in steps for key things (like building container images) and integrations can implement their own (like Azure integratiosn support provisioning). Developers can add to it...

Does your team have a Copilot subscription? The feature requires that.

If you do, I think this feature is still rolling out to users probably.

Right? Considering all the layers of complexity, I am surprised it works as often as it does.