Skip to content

Support setting functionapp kind on Azure Functions projects #8188

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
captainsafia opened this issue Mar 19, 2025 · 4 comments
Open

Support setting functionapp kind on Azure Functions projects #8188

captainsafia opened this issue Mar 19, 2025 · 4 comments
Labels
area-deployment azure Issues associated specifically with scenarios tied to using Azure azure-functions Issues related to the Azure Functions integration
Milestone

Comments

@captainsafia
Copy link
Member

To support Functions-specific deployment behaviors, we want to be able to assign the functionapp kind to the container app associated with the AzureFunctionsProjectResource during deployment time.

@captainsafia captainsafia added area-integrations Issues pertaining to Aspire Integrations packages azure-functions Issues related to the Azure Functions integration labels Mar 19, 2025
@captainsafia captainsafia added this to the Backlog milestone Mar 19, 2025
@captainsafia captainsafia self-assigned this Mar 19, 2025
@davidfowl davidfowl modified the milestones: Backlog, 9.3 Apr 18, 2025
@davidfowl davidfowl added the azure Issues associated specifically with scenarios tied to using Azure label Apr 18, 2025
@davidfowl
Copy link
Member

@captainsafia can you clarify where this gets set in the container app definition?

@captainsafia
Copy link
Member Author

See the sample below. I realize this isn't documented in the official definition.

@description('The location for the resource(s) to be deployed.')
param location string = resourceGroup().location

param storage_outputs_blobendpoint string

param storage_outputs_queueendpoint string

param storage_outputs_tableendpoint string

param messaging_outputs_servicebusendpoint string

param eventhubs_outputs_eventhubsendpoint string

param outputs_azure_container_registry_managed_identity_id string

param outputs_managed_identity_client_id string

param outputs_azure_container_apps_environment_id string

param outputs_azure_container_registry_endpoint string

param acanativefunctions_containerimage string

resource acanativefunctions 'Microsoft.App/containerApps@2024-10-02-preview' = {
  name: 'acanativefunctions'
  location: location
  properties: {
    configuration: {
      activeRevisionsMode: 'Single'
      ingress: {
        external: true
        targetPort: 8080
        transport: 'http'
      }
      registries: [
        {
          server: outputs_azure_container_registry_endpoint
          identity: outputs_azure_container_registry_managed_identity_id
        }
      ]
    }
    environmentId: outputs_azure_container_apps_environment_id
    template: {
      containers: [
        {
          image: acanativefunctions_containerimage
          name: 'acanativefunctions'
          env: []
      scale: {
        minReplicas: 1
      }
    }
  }
  identity: {
    type: 'UserAssigned'
    userAssignedIdentities: {
      '${outputs_azure_container_registry_managed_identity_id}': { }
    }
  }
  kind: 'functionapp' // here
}

@davidfowl
Copy link
Member

Ok top level

@mattchenderson
Copy link

Adding a link to Azure/azure-sdk-for-net#48417 which might be helpful if we can resolve it. It would probably simplify testing to be able to leverage PublishAsContainerApp for this until this work item is tackled.

I don't know how much codegen Azure.Provisioning is doing, but those docs are also typically built off of the service's Swagger, which is what would also be used for generation.

@davidfowl davidfowl modified the milestones: 9.3, 9.4 May 9, 2025
@davidfowl davidfowl added area-deployment and removed area-integrations Issues pertaining to Aspire Integrations packages labels May 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-deployment azure Issues associated specifically with scenarios tied to using Azure azure-functions Issues related to the Azure Functions integration
Projects
None yet
Development

No branches or pull requests

3 participants