AzurePublishingContext Properties
public bool ExcludeMainBicepFile { get; set; }Remarks
Callers of this class might not need main.bicep. A publisher that deploys each resource module directly from its own deployment manifest never consumes the root template. Although Azure.Provisioning can emit that template, a later Bicep compilation can fail for models the individual modules handle correctly. For example, the generated root always passes location to each module, but a tenant-scoped module does not declare a location parameter, resulting in BCP037.
When set to true, Azure still writes every per-resource Bicep module and populates Azure and Azure against Azure. Azure remains available in memory, but it is never built, compiled, or written to disk. The default is false.
public Infrastructure MainInfrastructure { get; }public Dictionary<BicepOutputReference, ProvisioningOutput> OutputLookup { get; }Remarks
Provisioning.ProvisioningOutput of the AzurePublishingContext.MainInfrastructure that was created with the value of the output referenced by the Aspire BicepOutputReference . public Dictionary<ParameterResource, ProvisioningParameter> ParameterLookup { get; }Remarks
Provisioning.ProvisioningParameter of the AzurePublishingContext.MainInfrastructure that was created to be filled with the value of the Aspire ApplicationModel.ParameterResource .