Azure / azure-resource-manager-schemas

Schemas used to author and validate Resource Manager Templates. These schemas power the intellisense and syntax completion in our ARM Tools VSCode extension, as well as the Export Template API
MIT License
611 stars 518 forks source link

2015-07-01 version of Microsoft.Authorization/roleAssignments no longer appears in schemas #1471

Open StephenWeatherford opened 3 years ago

StephenWeatherford commented 3 years ago

NOTE: This is not blocking the ARM extension but will affect users with the 2015-07-01 version of roleAssignments (or they can update to a newer version).

{
   "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
   "contentVersion": "1.0.0.0",
   "parameters": {
      "policyDefinitionId": {
         "type": "string"
      },
      "parameters": {
         "type": "object"
      }
   },
   "variables": {},
   "resources": [
      {
         "type": "Microsoft.Authorization/roleAssignments",
         "apiVersion": "2015-07-01",
         "name": "mgname-test",
         // THIS SHOULD FAIL IN RG DEPLOYMENT
         "location": "[deployment().location]",
         "properties": {
            "displayName": "test",
            "description": "test",
            "scope": "/providers/Microsoft.Management/managementGroups/mgname",
            "policyDefinitionId": "[parameters('policyDefinitionId')]",
            "parameters": "[parameters('parameters')]",
            "metadata": {
               "assignedBy": "test"
            },
            "enforcementMode": "Default",
            "principalId": "foo",
            "roleDefinitionId": "foo"
         }
      }
   ]
}

Previous: image

Current: image

ghost commented 3 years ago

Hello @darshanhs90, @AshishGargMicrosoft! It looks like there is a schemas issue that needs your attention. Please investigate and confirm it is on your end. Thanks :smile:

Issue Details
NOTE: This is *not* blocking the ARM extension but will affect users with the 2015-07-01 version of roleAssignments (or they can update to a newer version). ``` { "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#", "contentVersion": "1.0.0.0", "parameters": { "policyDefinitionId": { "type": "string" }, "parameters": { "type": "object" } }, "variables": {}, "resources": [ { "type": "Microsoft.Authorization/roleAssignments", "apiVersion": "2015-07-01", "name": "mgname-test", // THIS SHOULD FAIL IN RG DEPLOYMENT "location": "[deployment().location]", "properties": { "displayName": "test", "description": "test", "scope": "/providers/Microsoft.Management/managementGroups/mgname", "policyDefinitionId": "[parameters('policyDefinitionId')]", "parameters": "[parameters('parameters')]", "metadata": { "assignedBy": "test" }, "enforcementMode": "Default", "principalId": "foo", "roleDefinitionId": "foo" } } ] } ``` Previous: ![image](https://user-images.githubusercontent.com/6913354/105114722-4c734780-5a7c-11eb-9989-db0f1b5d3d1d.png) Current: ![image](https://user-images.githubusercontent.com/6913354/105114651-29489800-5a7c-11eb-8963-e77d5210ba38.png)
Author: StephenWeatherford
Assignees: -
Labels: `Needs: Triage :mag_right:`, `RP:Authorization`
Milestone: -
azcloudfarmer commented 3 years ago

Hi @stankovski can you please investigate on your end?