🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 13711

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 13711"

@philliphoff should we be using latest for the image tag or would it be better to pin to a specific version and then increment periodically? For things like Postgres we pin to a specific version but for Azure services sometimes the emulators are preferred to always use the latest so the engineering team for the service can ensure people are testing against a version that best represents what is on the service.

@philliphoff what happens if I do this:

var ts = builder.AddTaskScheduler(...)
var th = builder.AddTaskHub(...)
ts.RunAsEmulator(...)

Do the dashboard links work?

Lets put the <example> outside the <remarks>

Once that is done I'm good to see this go in. How do we want to communicate this one to users, this'll probably go out in February at some time, is it worth mentioning at that time on the Azure Functions blogs/channels (will obviously be in our release notes).

Do the dashboard links work?

@mitchdenny Good catch; it did not. I've fixed it (by deferring the IsEmulator test until the resource ready callback).

should we be using latest for the image tag or would it be better to pin to a specific version and then increment periodically? For things like Postgres we pin to a specific version but for Azure services sometimes the emulators are preferred to always use the latest so the engineering team for the service can ensure people are testing against a version that best represents what is on the service.

@mitchdenny For better or worse, DTS publishes only the latest tag.

How do we want to communicate this one to users, this'll probably go out in February at some time, is it worth mentioning at that time on the Azure Functions blogs/channels (will obviously be in our release notes).

@mitchdenny I'll talk to our PMs to see if/how they'd like to communicate the new feature.

@mitchdenny Just a friendly ping; please let me know if there's anything else needed in order for this to get in.

When this is merged, I should have a quick follow up that adds DTS support for publish and deployment (see work in progress).