Attempting to deploy Raygun to Azure Container Apps via azd results in an error

[robertjf]

If I attempt to deploy the Raygun service, I get the following error:

ERROR: failed deploying service 'Raygun': generating container app manifest: configuring ingress for resource Raygun: Binding http can't be mapped to main ingress because it has port 24605 defined. main ingress only supports port 80 for http scheme.

This also is a problem when attempting to synthesize the infrastructure etc.

[ProRedCat]

Thanks for bringing this to our attention. Before we dive into potential solutions, I'd like to get a better picture of what you're trying to achieve. Could you help me understand a few things about your setup?

• What kind of environment are you deploying to? Is this a production, staging, or some other type of setup?
• Are you intentionally trying to deploy the Raygun service to Azure, or did you expect it to be excluded from the deployment?

Once we have a clearer picture of your setup, we'll be in a better position to guide you towards the best solution. Looking forward to your response!

Raygun4Aspire is intended for local development rather than deployment, so we're just trying to get an idea around what is expected here.

[robertjf]

Hey, we've been using it for local dev testing, but of course I haven't yet found a way to "silo" it off so azd doesn't pick it up - I've effectively had to remove it entirely from the code for deployment.