This message was deleted.
# azure
s
This message was deleted.
s
Hey Dan. IIRC the arm2pulumi converter only generates the
invokeAsync
when location is not specified for resources in the arm templates and it tries to determine by querying the resource group. We are about to add support for inferring the default location from the resource group (i.e. fix https://github.com/pulumi/pulumi-azure-nextgen/issues/6 - should be in the next release) directly in the provider. In which case arm2pulumi would no longer generate the
invokeAsync
anymore and hopefully all other references can stick to the resource-group name instead. Are there other situations outside of location inference that the
invokeAsync
is being called for you?
t
I'm not sure that issue addresses this as the resource group location doesn't need to be present in ARM templates (we just use
resourcegroup().location
), but I'd be happy to require one in the config if it meant I could avoid
InvokeAsync
.
s
ah yes, sorry I missed the obvious
resourcegroup().location
use case - this will emit the
invokeAsync
. If you omit it in the arm template, invokeAsync will be avoided since the provider will take care of that resolution itself in the next release
👍 1