magodo
@Dipak-Mistry-WTW The PR #36623 is yet merged.
@mpjtaylor Thank you for submitting this issue! I've created a PR to update the underlying SDK. Once it's merged, we shall be able to *delete the share with the include-leased...
@aneeraj There is one typo in the previous PR, and I've submitted one more PR to fix that. This is to support the functionality via the data plane API. Since...
@paul-hugill From the azuread provider's issue, the diff indicates a change for the `approval_stage`. Is that the same for your case (as the plan diff you provided doesn't look like...
The issue probably lies in https://github.com/hashicorp/terraform-provider-azurerm/blob/9d1768c6a074a460cd059efc4285f6a7832aa14a/internal/services/authorization/role_management_policy.go#L268-L272 This happens at Create/Update that no `approval_stage` is specified, it ended up with an empty block, while actually it wants a `null`. Ping @manicminer.
At the first glance, this is either an issue at the Azure CLI side, or an issue at the Terraform SDK side (it also caches the token): https://github.com/hashicorp/go-azure-sdk/blob/4d383f2a389cf5073e8b5d0469f535e181b1a51c/sdk/auth/cached_authorizer.go#L29-L45 ``` func...
Hi @robbert-nlo, thank you for the additional information and analysis! At the Terraform provider side, as I have demonstrated, it has a process lock, which restricts there is only one...
@robbert-nlo OK, the storage data plane clients maintain their own authorizers, this means it is possible that multiple authorizers are using the Azure CLI in parallel (each has its own...
This bug is being tracked in #2063, which I'm going to close this in favour of - would you mind subscribing to that issue for updates? Thanks!
This bug is being tracked in #2063, which I'm going to close this in favour of - would you mind subscribing to that issue for updates? Thanks!