Is there an existing issue for this?
Describe the bug
Referencing existing Foundry resource and project resource automatically deploys a capabilityHosts subresource and hangs until it is deployed.
I found ClearDefaultRoleAssignments to prevent role deployments (also an annoying one) but there is no clear way to disable the capabilityHosts deployment.
Expected Behavior
Referencing existing resources should not start deploying things. Especially not without confirmation by the user.
Steps To Reproduce
Have an existing Foundry resource with an existing project.
Add Aspire.Hosting.Foundry 13.5.4-preview.1.26464.4 to your project
Run
var existingFoundryName = builder.AddParameter("existingFoundryName");
var existingFoundryProject = builder.AddParameter("existingFoundryProject");
var existingFoundryResourceGroup = builder.AddParameter("existingFoundryResourceGroup");
var foundry = builder.AddFoundry("foundry")
.AsExisting(existingFoundryName, existingFoundryResourceGroup)
.ClearDefaultRoleAssignments();
var foundryProject = foundry.AddProject("foundry-project")
.AsExisting(existingFoundryProject, existingFoundryResourceGroup);
Exceptions (if any)
No response
Aspire doctor output
Anything else?
No response
Is there an existing issue for this?
Describe the bug
Referencing existing Foundry resource and project resource automatically deploys a capabilityHosts subresource and hangs until it is deployed.
I found ClearDefaultRoleAssignments to prevent role deployments (also an annoying one) but there is no clear way to disable the capabilityHosts deployment.
Expected Behavior
Referencing existing resources should not start deploying things. Especially not without confirmation by the user.
Steps To Reproduce
Have an existing Foundry resource with an existing project.
Add Aspire.Hosting.Foundry 13.5.4-preview.1.26464.4 to your project
Run
Exceptions (if any)
No response
Aspire doctor output
Anything else?
No response