Microsoft.DataFactory/factories/integrationruntimes Microsoft.DataFactory/datafactories/gateways Microsoft.ContainerService/managedClusters/accessProfiles Microsoft.ContainerService/managedClusters Microsoft.ContainerRegistry/registries/tasks Microsoft.ContainerRegistry/registries/runs Microsoft.ContainerRegistry/registries/webhooks Microsoft.ContainerRegistry/registries/taskruns Microsoft.ContainerRegistry/registries/buildTasks/steps Microsoft.ContainerRegistry/registries/buildTasks Microsoft.ContainerRegistry/registries/agentpools Microsoft.BotService/botServices/channels Microsoft.BatchAI/workspaces/experiments/jobs Microsoft.AppConfiguration/configurationStores Microsoft.ApiManagement/service/subscriptions Microsoft.ApiManagement/service/openidConnectProviders Microsoft.ApiManagement/service/namedValues Microsoft.ApiManagement/service/identityProviders Microsoft.ApiManagement/service/authorizationServers The possible uses of list* are shown in the following table. You can't use them with count because the count must be determined before the list function is resolved. When used with property iteration, you can use the list functions for input because the expression is assigned to the resource property. Output values are stored in the deployment history and could be retrieved by a malicious user. Don't use a list function that exposes sensitive information in the outputs section of a template. The list functions can be used in the properties of a resource definition. An example of passing function values is shown in this article. Only provide this object for functions that support receiving an object with parameter values, such as listAccountSas on a storage account. Typically, in the format, yyyy-mm-dd.Īn object that has values for the function.
Parameters ParameterĪPI version of resource runtime state. Some common usages are list, listKeys, listKeyValue, and listSecrets. The operation name must start with list and may have a suffix. Each implementation returns values for the resource type that supports a list operation. The syntax for this function varies by name of the list operations.
The basic format of the resource ID returned by this function is: (resourceName or resourceIdentifier, apiVersion, functionValues) Type of the extension resource including resource provider namespace.Ĭontinue adding resource names as parameters when the resource type includes more segments. The resource ID for the resource that the extension resource is applied to. In Bicep, use the extensionResourceId function. An extension resource is a resource type that's applied to another resource to add to its capabilities. Returns the resource ID for an extension resource. extensionResourceIdĮxtensionResourceId(baseResourceId, resourceType, resourceName1,. We recommend Bicep because it offers the same capabilities as ARM templates and the syntax is easier to use.
0 kommentar(er)
