Skip to content

[Automated] Update API Surface Area#9359

Merged
joperezr merged 1 commit intomainfrom
update-api-diffs
Jul 30, 2025
Merged

[Automated] Update API Surface Area#9359
joperezr merged 1 commit intomainfrom
update-api-diffs

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Auto-generated update to the API surface to compare current surface vs latest release. This should only be merged once this surface area ships in a new release.

@github-actions github-actions Bot added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label May 16, 2025
@github-actions github-actions Bot added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label May 16, 2025
@github-actions github-actions Bot force-pushed the update-api-diffs branch from 36e4703 to ab59e2a Compare May 17, 2025 16:17
@davidfowl
Copy link
Copy Markdown
Contributor

@joperezr @eerhardt Some of these changes should be in 9.3, do we know what's happening?

@github-actions github-actions Bot force-pushed the update-api-diffs branch from ab59e2a to 64b1917 Compare May 18, 2025 16:17
@eerhardt
Copy link
Copy Markdown
Member

Some of these changes should be in 9.3, do we know what's happening?

Yes, main and release/9.3 are out of sync. We need to merge release/9.3 into main.

@github-actions github-actions Bot force-pushed the update-api-diffs branch 2 times, most recently from a009283 to 112736d Compare May 20, 2025 16:18
Comment thread src/Aspire.Hosting/api/Aspire.Hosting.cs Outdated
@joperezr
Copy link
Copy Markdown
Member

Some of these changes should be in 9.3, do we know what's happening?

Yes, main and release/9.3 are out of sync. We need to merge release/9.3 into main.

That was done yesterday, so I'd expect things to look correct now.

Comment thread src/Aspire.Hosting.Milvus/api/Aspire.Hosting.Milvus.cs
@github-actions github-actions Bot force-pushed the update-api-diffs branch 7 times, most recently from b50c898 to e4b32b6 Compare May 28, 2025 16:18
@github-actions github-actions Bot force-pushed the update-api-diffs branch 3 times, most recently from 6429680 to 8d86d5b Compare May 31, 2025 16:17
@github-actions github-actions Bot force-pushed the update-api-diffs branch 2 times, most recently from 1e8fa0b to f2c4a2c Compare July 2, 2025 16:19
@eerhardt eerhardt mentioned this pull request Jul 3, 2025
16 tasks
@github-actions github-actions Bot force-pushed the update-api-diffs branch 7 times, most recently from 49666f5 to c97ed34 Compare July 10, 2025 16:19
@github-actions github-actions Bot force-pushed the update-api-diffs branch 7 times, most recently from e7648e6 to 9c42e4e Compare July 16, 2025 23:56
public static bool IsEmulator(this ApplicationModel.IResource resource) { throw null; }
}

public static partial class EventingExtensions
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we call this DistributedApplicationEventingExtensions for consistency? /cc @davidfowl

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yea

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread src/Aspire.Hosting/api/Aspire.Hosting.cs
{
public static ApplicationModel.IResourceBuilder<ExternalServiceResource> AddExternalService(this IDistributedApplicationBuilder builder, string name, ApplicationModel.IResourceBuilder<ApplicationModel.ParameterResource> urlParameter) { throw null; }

public static ApplicationModel.IResourceBuilder<ExternalServiceResource> AddExternalService(this IDistributedApplicationBuilder builder, string name, string url) { throw null; }
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: should this be string uri. I know that we have Uri uri, but there is no reason that the string has to be a URL :)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless it is very specifically HTTP/HTTPS only in which case should the API be called AddExternalHttpService(...)? /cc @DamianEdwards

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It does, we validate it.

Comment thread src/Aspire.Hosting/api/Aspire.Hosting.cs

[System.Diagnostics.CodeAnalysis.Experimental("ASPIREPUBLISHERS001", UrlFormat = "https://aka.ms/aspire/diagnostics/{0}")]
public partial interface IPublishingActivityProgressReporter
public partial interface IPublishingActivityReporter
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a better name would be IPipelineActivityReporter, as this isn't specific to "publishing" and it's already used in a "deploying" context as well. Ideally, pipeline could be used here as its agnostic to both publishing and deploying.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think just IActivityReporter.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That seems too generic.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pipeline doesn't mean anything yet. IOperationActivityReporter 😄

Copy link
Copy Markdown
Member

@IEvangelist IEvangelist Jul 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pipeline doesn't mean anything yet.

Sure it does! It's the line we draw between a user on the CLI calling publish or deploy and the output on their screen. 😝 That's where this is used.

IOperationActivityReporter

Too generic.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pipeline doesn’t mean much

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think Operation makes sense - because we have publish and run operations - and we'll probably want to add prompting support for run as well.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose that if we make it clear that Operation represents Steps and child Tasks—which are distinct to non-run ops.

public partial interface IPublishingActivityProgressReporter
public partial interface IPublishingActivityReporter
{
System.Threading.Tasks.Task CompletePublishAsync(string? completionMessage = null, CompletionState? completionState = null, bool isDeploy = false, System.Threading.CancellationToken cancellationToken = default);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead, consider CompletePipelineAsync as this API is used in deploying as well.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should just be CompleteAsync

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't feel like it;s for 9.4, this API is experimental

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think renaming it to CompleteAsync makes the isDeploy parameter even more awkward.

Can the IPublishingActivityReporter know ambiently if it is a deploy operation or not?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO, CompleteAsync is too vague considering there are 3 distinct concepts that can be completed here (the publish/deploy itself, steps, and tasks).

Can the IPublishingActivityReporter know ambiently if it is a deploy operation or not?

Nope, we'd have to modify this API to take PublishingOptions as input if we wanted to determine this without having an isDeploy argument.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There should be no isDeploy parameter. It should jsut take a message.

}

[System.Diagnostics.CodeAnalysis.Experimental("ASPIREPUBLISHERS001", UrlFormat = "https://aka.ms/aspire/diagnostics/{0}")]
public partial interface IPublishingStep : System.IAsyncDisposable
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider renaming this to IPipelineStep, as it's used in both publish and deploy.

}

[System.Diagnostics.CodeAnalysis.Experimental("ASPIREPUBLISHERS001", UrlFormat = "https://aka.ms/aspire/diagnostics/{0}")]
public partial interface IPublishingTask : System.IAsyncDisposable
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider renaming this to IPipelineTask, as it's used in both publish and deploy.

@davidfowl
Copy link
Copy Markdown
Contributor

@joperezr can we merge this

@joperezr
Copy link
Copy Markdown
Member

On it, just need to rerun real quick

@joperezr
Copy link
Copy Markdown
Member

Merged with end state as of release 9.4.0. Thanks everyone!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) Re-opened Github-Action PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants