resources.resjson

{
  "loc.friendlyName": "ARM template deployment",
  "loc.helpMarkDown": "[Learn more about this task](https://aka.ms/armtaskreadme)",
  "loc.description": "Deploy an Azure Resource Manager (ARM) template to all the deployment scopes",
  "loc.instanceNameFormat": "ARM Template deployment: $(deploymentScope) scope",
  "loc.releaseNotes": "- Added support for bicepparam.",
  "loc.group.displayName.AzureDetails": "Azure Details",
  "loc.group.displayName.Template": "Template",
  "loc.group.displayName.Advanced": "Advanced",
  "loc.input.label.deploymentScope": "Deployment scope",
  "loc.input.help.deploymentScope": "Deployment scope of the deployment. To know more abour deployment scopes, refer this [link](https://docs.microsoft.com/bs-latn-ba/Azure/azure-resource-manager/resource-group-template-deploy-rest#deployment-scope)",
  "loc.input.label.ConnectedServiceName": "Azure Resource Manager connection",
  "loc.input.help.ConnectedServiceName": "Select the Azure Resource Manager service connection having access to the selected deployment scope.",
  "loc.input.label.subscriptionName": "Subscription",
  "loc.input.help.subscriptionName": "Select the Azure subscription",
  "loc.input.label.action": "Action",
  "loc.input.help.action": "Action to be performed on the Azure resources or resource group.",
  "loc.input.label.resourceGroupName": "Resource group",
  "loc.input.help.resourceGroupName": "Provide the name of a resource group.",
  "loc.input.label.location": "Location",
  "loc.input.help.location": "For Resource Group deployment scope: Location for deploying the resource group. If the resource group already exists in the subscription, then this value will be ignored.\n For other deployment scope: Location to store deployment metadata.",
  "loc.input.label.templateLocation": "Template location",
  "loc.input.label.csmFileLink": "Template link",
  "loc.input.help.csmFileLink": "Specify the URL of the template file. Example: [https://raw.githubusercontent.com/Azure/...](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/101-vm-simple-windows/azuredeploy.json) \n\nTo deploy a template stored in a private storage account, retrieve and include the shared access signature (SAS) token in the URL of the template. Example: `<blob_storage_url>/template.json?<SAStoken>` To upload a template file (or a linked template) to a storage account and generate a SAS token, you could use [Azure file copy](https://aka.ms/azurefilecopyreadme) task or follow the steps using [PowerShell](https://go.microsoft.com/fwlink/?linkid=838080) or [Azure CLI](https://go.microsoft.com/fwlink/?linkid=836911).\n\nTo  view the template parameters in a grid, click on “…” next to Override template parameters text box. This feature requires that CORS rules are enabled at the source. If templates are in Azure storage blob, refer to [this](https://docs.microsoft.com/en-us/rest/api/storageservices/fileservices/Cross-Origin-Resource-Sharing--CORS--Support-for-the-Azure-Storage-Services?redirectedfrom=MSDN#understanding-cors-requests) to enable CORS.",
  "loc.input.label.csmParametersFileLink": "Template parameters link",
  "loc.input.help.csmParametersFileLink": "Specify the URL of the parameters file. Example: [https://raw.githubusercontent.com/Azure/...](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/101-vm-simple-windows/azuredeploy.parameters.json) \n\nTo use a file stored in a private storage account, retrieve and include the shared access signature (SAS) token in the URL of the template. Example: `<blob_storage_url>/template.json?<SAStoken>` To upload a parameters file to a storage account and generate a SAS token, you could use [Azure file copy](https://aka.ms/azurefilecopyreadme) task or follow the steps using [PowerShell](https://go.microsoft.com/fwlink/?linkid=838080) or [Azure CLI](https://go.microsoft.com/fwlink/?linkid=836911). \n\nTo  view the template parameters in a grid, click on “…” next to Override template parameters text box. This feature requires that CORS rules are enabled at the source. If templates are in Azure storage blob, refer to [this](https://docs.microsoft.com/en-us/rest/api/storageservices/fileservices/Cross-Origin-Resource-Sharing--CORS--Support-for-the-Azure-Storage-Services?redirectedfrom=MSDN#understanding-cors-requests) to enable CORS.",
  "loc.input.label.csmFile": "Template",
  "loc.input.help.csmFile": "Specify the path or a pattern pointing to the Azure Resource Manager template. For more information about the templates see https://aka.ms/azuretemplates. To get started immediately use template https://aka.ms/sampletemplate. 'Linked artifact' also has support for Bicep files when the Azure CLI version > 2.20.0",
  "loc.input.label.csmParametersFile": "Template parameters",
  "loc.input.help.csmParametersFile": "Specify the path or a pattern pointing for the parameters file for the Azure Resource Manager template. 'Linked artifact' also has support for Bicep files when the Azure CLI version > 2.20.0",
  "loc.input.label.overrideParameters": "Override template parameters",
  "loc.input.help.overrideParameters": "To view the template parameters in a grid, click on “…” next to Override Parameters textbox. This feature requires that CORS rules are enabled at the source. If templates are in Azure storage blob, refer to [this](https://docs.microsoft.com/en-us/rest/api/storageservices/fileservices/Cross-Origin-Resource-Sharing--CORS--Support-for-the-Azure-Storage-Services?redirectedfrom=MSDN#understanding-cors-requests) to enable CORS. Or type the template parameters to override in the textbox. Example, <br>–storageName fabrikam –adminUsername $(vmusername) -adminPassword $(password) –azureKeyVaultName $(fabrikamFibre).<br>If the parameter value you're using has multiple words, enclose them in quotes, even if you're passing them using variables. For example, -name \"parameter value\" -name2 \"$(var)\"<br>To override object type parameters use stringified JSON objects. For example, -options [\"option1\"] -map {\"key1\": \"value1\" }. ",
  "loc.input.label.deploymentMode": "Deployment mode",
  "loc.input.help.deploymentMode": "Refer to [this](https://docs.microsoft.com/en-us/azure/azure-resource-manager/deployment-modes) for more details. \n\n Incremental mode handles deployments as incremental updates to the resource group. It leaves unchanged resources that exist in the resource group but are not specified in the template. \n\n Complete mode deletes resources that are not in your template. Complete mode takes relatively more time than incremental mode. If the task times out, consider increasing the timeout, or changing the mode to 'Incremental'. \n **[Warning] Complete mode will delete all the existing resources in the resource group that are not specified in the template. Do review if the resource group you're deploying to doesn't contain any necessary resources that are not specified in the template.** \n\n Validate mode enables you to find problems with the template before creating actual resources. Validate mode enables you to find problems with the template before creating actual resources. Please note that this mode will anyways create a resource group even if it does not deploy any resource.\n\n By default, Incremental mode is used.",
  "loc.input.label.deploymentName": "Deployment name",
  "loc.input.help.deploymentName": "Specifies the name of the resource group deployment to create.",
  "loc.input.label.deploymentOutputs": "Deployment outputs",
  "loc.input.help.deploymentOutputs": "Provide a name for the variable for the output variable which will contain the outputs section of the current deployment object in string format. You can use the “ConvertFrom-Json” PowerShell cmdlet to parse the JSON object and access the individual output values. For more details refer to [this](https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzureResourceManagerTemplateDeploymentV3#deployment-outputs)",
  "loc.input.label.addSpnToEnvironment": "Access service principal details in override parameters",
  "loc.input.help.addSpnToEnvironment": "Adds service principal id and key of the Azure endpoint you chose to the script's execution environment. You can use these variables: `$servicePrincipalId` and `$servicePrincipalKey` in your override parameters like `-key $servicePrincipalKey`",
  "loc.input.label.useWithoutJSON": "Use individual output values without JSON.Stringify applied",
  "loc.input.help.useWithoutJSON": "Individual output values are being converted via JSON.Stringify by default. If you want to use the output values as it is without converting them via JSON.Stringify, enable this option. For more details refer to [this](https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzureResourceManagerTemplateDeploymentV3#deployment-outputs)",
  "loc.messages.CheckResourceGroupExistence": "Checking if the following resource group exists: %s.",
  "loc.messages.ResourceGroupStatusFetchFailed": "Failed to check the resource group status. Error: %s.",
  "loc.messages.ResourceGroupStatus": "Resource group exists: %s.",
  "loc.messages.ResourceGroupCreationFailed": "Failed to create the resource group. Error: %s",
  "loc.messages.CreatingNewRG": "Creating resource Group: %s",
  "loc.messages.CreatedRG": "Resource Group created successfully.",
  "loc.messages.CreatingTemplateDeployment": "Creating deployment parameters.",
  "loc.messages.TemplateParsingFailed": "Ensure the Template file ( '%s' ) is valid. Task failed while parsing with following error: %s",
  "loc.messages.FileFetchFailed": "Failed to download the file. URL: '%s'. Error: %s",
  "loc.messages.ParametersFileParsingFailed": "Ensure the Parameters file ( '%s' ) is valid. Task failed while parsing with following error: %s",
  "loc.messages.StartingDeployment": "Starting Deployment.",
  "loc.messages.CreateTemplateDeploymentSucceeded": "Successfully deployed the template.",
  "loc.messages.CreateTemplateDeploymentFailed": "Task failed while creating or updating the template deployment.",
  "loc.messages.ErrorsInYourDeployment": "There were errors in your deployment. Error code: %s.",
  "loc.messages.Details": "Details:",
  "loc.messages.ErrorType": "Error Type:",
  "loc.messages.PolicyDefinitionName": "Policy Definition Name :",
  "loc.messages.PolicyAssignmentName": "Policy Assignment Name :",
  "loc.messages.StartingValidation": "Starting template validation.",
  "loc.messages.ValidDeployment": "Template deployment validation was completed successfully.",
  "loc.messages.CreateTemplateDeploymentValidationFailed": "Template validation failed. Error: %s.",
  "loc.messages.DeletingResourceGroup": "Deleting resource group: %s",
  "loc.messages.CouldNotDeletedResourceGroup": "Could not delete resource group: '%s'. Operation failed with error: %s",
  "loc.messages.DeletedResourceGroup": "Deleted resource group: %s",
  "loc.messages.InvalidAction": "This action is not defined. Check with the task author.",
  "loc.messages.ARGD_ConstructorFailed": "Task failed while initializing. Error: %s",
  "loc.messages.InvalidTemplateLocation": "The template location supplied is invalid. Task only supports 'Linked artifact' or 'URL of the file'",
  "loc.messages.EncodingNotSupported": "Encoding of the file '%s' is '%s' which is not supported. Supported file encodings are ['utf-8', 'utf-16le']",
  "loc.messages.CouldNotDetectEncoding": "Could not detect encoding of file '%s'",
  "loc.messages.DetectedFileEncoding": "The detected encoding for file '%s' is '%s'",
  "loc.messages.ErrorWhileParsingParameter": "There was an error while overriding '%s' parameter because of '%s', make sure it follows JavaScript Object Notation (JSON)",
  "loc.messages.TemplateFilePatternMatchingMoreThanOneFile": "Found multiple files matching template file pattern: %s",
  "loc.messages.TemplateParameterFilePatternMatchingMoreThanOneFile": "Found multiple files matching template parameters file pattern: %s",
  "loc.messages.TemplateFilePatternMatchingNoFile": "Could not find any file matching the template file pattern",
  "loc.messages.TemplateParameterFilePatternMatchingNoFile": "Could not find any file matching the template file pattern",
  "loc.messages.ParametersPatternMatchesADirectoryInsteadOfAFile": "Parameters file pattern matches a directory instead of a file.",
  "loc.messages.CsmFilePatternMatchesADirectoryInsteadOfAFile": "Template file pattern matches a directory instead of a file: %s",
  "loc.messages.AddedOutputVariable": "Updated output variable '%s', which contains the outputs section of the current deployment object in string format.",
  "loc.messages.UnableToReadResponseBody": "Unable to read response body. Error: %s",
  "loc.messages.MoreInformationOnAzurePortal": "More information on Azure Portal",
  "loc.messages.LogDeploymentName": "Deployment name is %s",
  "loc.messages.ResourceGroupNameNotProvided": "Resource Group name should be provided",
  "loc.messages.LocationNotProvided": "Location is required for deployment",
  "loc.messages.ARMServiceConnectionScope": "ARM Service Connection deployment scope - %s",
  "loc.messages.ServicePrincipalRoleAssignmentDetails": "Please make sure the Service Principal with name %s is assigned the right roles for the entity %s. Follow the link for more details: https://docs.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal",
  "loc.messages.ServicePrincipalFetchFailed": "Error while fetching Service Principal details: %s",
  "loc.messages.FindMoreDeploymentDetailsAzurePortal": "Task successfully created an Azure Resource Manager deployment, but the deployment failed. Please see more detailed Azure resource manager deployment logs at: (Please Copy-Paste the link) %s",
  "loc.messages.ManagedServiceIdentityDetails": "Please make sure the Managed Service Identity used for deployment is assigned the right roles for the Resource Group %s. Follow the link for more details: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/howto-assign-access-portal",
  "loc.messages.CompleteDeploymentModeNotSupported": "Deployment mode 'Complete' is not supported for deployment at '%s' scope",
  "loc.messages.TemplateValidationFailure": "Validation errors were found in the Azure Resource Manager template. This can potentially cause template deployment to fail. %s. Please follow https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-syntax",
  "loc.messages.TroubleshootingGuide": "Check out the troubleshooting guide to see if your issue is addressed: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment?view=azure-devops#troubleshooting",
  "loc.messages.IncompatibleAzureCLIVersion": "Azure CLI version should be >= 2.20.0",
  "loc.messages.AzureCLINotFound": "Azure CLI not found on the agent.",
  "loc.messages.FailedToFetchAzureCLIVersion": "Failed to fetch az cli version from agent. Error: %s",
  "loc.messages.BicepBuildFailed": "\"az bicep build\" failed. Error: %s",
  "loc.messages.BicepFileCleanupFailed": "Failed to delete Bicep file. Error: %s",
  "loc.messages.LoginFailed": "Azure login failed: %s",
  "loc.messages.MSILoginFailed": "Azure login failed using Managed Service Identity: %s",
  "loc.messages.AuthSchemeNotSupported": "Auth Scheme %s is not supported",
  "loc.messages.ErrorInSettingUpSubscription": "Error in setting up subscription: %s",
  "loc.messages.BicepParamBuildFailed": "\"az bicep build-param\" failed. Error: %s",
  "loc.messages.IncompatibleAzureCLIVersionBicepParam": "Azure CLI version should be >= 2.47.0 to use .bicepparam file",
  "loc.messages.ErrorWhileOverrideParameterUndefined": "The provided metadata file '%s'  is missing metadata of parameter '%s'"
}