No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I think I got it...

```  new function_apps.WebApp("reportApp", {
    name: `${reportContainerAppName}`,
    resourceGroupName: resourceGroupLinuxFunctionApp.name,
    kind: "functionapp,linux,container,azurecontainerapps",
    managedEnvironmentId: managedEnvironment.id,
...```

although, doesn't seem to work

```azure-native:web/v20220901:WebApp reportApp creating (3s) error: Code="BadRequest" Message="Invalid parameter. NetFrameworkVersion is not supported for Azure Functions on Azure Container apps. Please retry the operation without NetFrameworkVersion." Details=[{"Message":"Invalid parameter. NetFrameworkVersion is not supported for Azure Functions on Azure Container apps. Please retry the operation without NetFrameworkVersion."},{"Code":"BadRequest"},{"ErrorEntity":{"Code":"BadRequest","Message":"Invalid parameter. NetFrameworkVersion is not supported for Azure Functions on Azure Container apps. Please retry the operation without NetFrameworkVersion."}}]```
I'm not setting `NetFrameworkVersion` anywhere in my code. No idea where that's coming from.

so, had to set that to `""`, otherwise deployments would fail.
Also, can't use managed identity to pull from ACR, wow.

I can look when I’m back but all our container apps stuff is behind reverse-proxy.  For a function that is an http trigger, should be able to interact by forwarding the http request to the container.

dumb question but are you using the `<http://mcr.microsoft.com/azure-functions/dotnet:4|mcr.microsoft.com/azure-functions/dotnet:4>` container?

image.png

As for env vars related to function apps setup when pulumi runs

The only container that has external ingress is reverse-proxy, <https://github.com/microsoft/reverse-proxy>