Microsoft.Web sites/slots/functions 2018-11-01

  • مقالة
  • قراءة خلال 2 دقائق

The sites/slots/functions resource type can be deployed to: Resource groups.

To learn about resource group deployments, see Bicep or ARM template.

Template format

To create a Microsoft.Web/sites/slots/functions resource, add the following Bicep or JSON to your template.

resource symbolicname 'Microsoft.Web/sites/slots/functions@2018-11-01' = {
  name: 'string'
  kind: 'string'
  parent: resourceSymbolicName
  properties: {
    config: any()
    config_href: 'string'
    files: {}
    function_app_id: 'string'
    href: 'string'
    script_href: 'string'
    script_root_path_href: 'string'
    secrets_file_href: 'string'
    test_data: 'string'
  }
}

Property values

sites/slots/functions

Name Description Value
type The resource type

For Bicep, set this value in the resource declaration.		 'Microsoft.Web/sites/slots/functions'
apiVersion The resource api version

For Bicep, set this value in the resource declaration.		 '2018-11-01'
name The resource name

See how to set names and types for child resources in Bicep or JSON ARM templates.		 string (required)
kind Kind of resource. string
parent In Bicep, you can specify the parent resource for a child resource. You only need to add this property when the child resource is declared outside of the parent resource.

For more information, see Child resource outside parent resource.		 Symbolic name for resource of type: slots
properties FunctionEnvelope resource specific properties FunctionEnvelopeProperties

FunctionEnvelopeProperties

Name Description Value
config Any object For Bicep, you can use the any() function.
config_href Config URI. string
files File list. object
function_app_id Function App ID. string
href Function URI. string
script_href Script URI. string
script_root_path_href Script root path URI. string
secrets_file_href Secrets file URI. string
test_data Test data used when testing via the Azure Portal. string