brave-angle-33257
10/26/2018, 10:31 PMDo you want to perform this update? yes
Updating (LightstreamStudio/core-msi-stage):
Type Name Status Info
pulumi:pulumi:Stack core-msi-core-msi-stage
+ ├─ azure:msi:UserAssignedIdentity 93bfe621-3-wus-uai created
+ ├─ azure:msi:UserAssignedIdentity 93bfe621-3-weu-uai created
+ ├─ azure:msi:UserAssignedIdentity 93bfe621-3-scus-uai created
+ ├─ azure:msi:UserAssignedIdentity 93bfe621-3-uks-uai created
+ ├─ azure:msi:UserAssignedIdentity 93bfe621-3-eus2-uai created
~ └─ azure:role:Definition Reader And Blob Data Access - Lightstream **updating failed** [diff: ~assignableScopes]; 1 error
Diagnostics:
azure:role:Definition (Reader And Blob Data Access - Lightstream):
error: Plan apply failed: 1 error occurred:
* updating urn:pulumi:core-msi-stage::core-msi::azure:role/definition:Definition::Reader And Blob Data Access: authorization.RoleDefinitionsClient#CreateOrUpdate: Failure responding to request: StatusCode=409 -- Original Error: autorest/azure: Service returned an error. Status=409 Cod
e="RoleDefinitionWithSameNameExists" Message="A role definition cannot be updated with a name that already exists."
Resources:
5 changes
+ 5 created
21 unchanged
stocky-spoon-28903
10/26/2018, 10:32 PMbrave-angle-33257
10/26/2018, 10:33 PMstocky-spoon-28903
10/26/2018, 10:33 PMbrave-angle-33257
10/26/2018, 10:35 PM[diff: ~assignableScopes]; 1 error
Original Error: autorest/azure: Service returned an error. Status=409 Co$
e="RoleDefinitionWithSameNameExists" Message="A role definition cannot be updated with a name that already exists."
stocky-spoon-28903
10/26/2018, 10:35 PMbrave-angle-33257
10/26/2018, 10:36 PMwhite-balloon-205
assignable_scopes
should be marked as ForceNew
, or it is a bug in Azure itself.