DistributedApplicationPipelineExtensions Methods
ClassMethods2 members
Extension methods for
IDistributedApplicationPipeline . DisableBuildOnlyContainerValidation(IDistributedApplicationPipeline) Section titled DisableBuildOnlyContainerValidation(IDistributedApplicationPipeline)extensionI Disables the publish and deploy validation that requires build-only containers to be consumed by another resource.
public static class DistributedApplicationPipelineExtensions{ public static IDistributedApplicationPipeline DisableBuildOnlyContainerValidation( this IDistributedApplicationPipeline pipeline) { // ... }}Parameters
pipelineIReturns
IDistributedApplicationPipeline The distributed application pipeline for chaining.Remarks
This is an application-wide escape hatch for scenarios where the build-only container validation is too restrictive for a particular app. Prefer wiring build-only containers through
PublishWithContainerFiles or PublishWithStaticFiles when possible. WithFinalAction(IDistributedApplicationPipeline, string, Func<PipelineStepContext, Task>) Section titled WithFinalAction(IDistributedApplicationPipeline, string, Func<PipelineStepContext, Task>)extensionI Configures an action that runs after the named pipeline step and all of its dependencies complete.
public static class DistributedApplicationPipelineExtensions{ public static IDistributedApplicationPipeline WithFinalAction( this IDistributedApplicationPipeline pipeline, string stepName, Func<PipelineStepContext, Task> action) { // ... }}Parameters
pipelineIstepName stringThe name of the pipeline step.actionFunc<PipelineStepContext, Task> A final action to execute.Returns
IDistributedApplicationPipeline The distributed application pipeline for chaining.Exceptions
ArgumentNullException Thrown when pipeline, stepName , or action is null. ArgumentExceptionThrown when stepName is empty.InvalidOperationException Thrown during pipeline resolution when the named step does not exist. Remarks
The final action is configured when the pipeline graph is resolved, so it runs after dependencies added by resource annotations and other pipeline configuration callbacks. Multiple final actions for the same step execute sequentially in registration order. If a final action fails, subsequent final actions are not invoked.