Steven

Other considerations here @ms-henglu can we do them? 3. location listing 4. flatten map function to simplify for each expressions General guidance by Terraform is to avoid anything that requires...

@hqhqhqhqhqhqhqhqhqhqhq I think it would make sense to do option 1, since that would be consistent with the behavior of AzAPI (as `parent_id` is already a parameter in resource definitions)....

@matt-FFFFFF would you mind elaborating on why you prefer four separate functions compared to one function to construct resource IDs generically? Maybe with some scenarios. Would help us understand which...

Makes sense to me. @ms-henglu if you don't have any other concerns, I think we can move forward with this approach.

Love that we're doing this. Following this issue to see how the progress goes. We might be able to create a provider flag @ms-henglu to toggle on/off whether the state...

@ms-henglu if we tie the behavior of the provider behind a flag, it will still need the full data? Could I not store the smaller data overhead in state, change...

@ms-henglu can you take a look at gjson? I’ll also take a look. Thanks for the idea @matt-FFFFFF

@ms-henglu do we have a way of renewing the access token? If not we should definitely make sure to get that fixed for long running operations.

Thanks for the issue @kaplik! I'm struggling to repro this, as I'm running into a 400 myself. I'm wondering if this is a service-side issue. @ms-henglu can you take a...

Makes sense. It looks like there's somewhere within the resource's API that is allowing you to create the resource without a specified location and sets it to global in the...