magodo
@tadelesh It is explained in the description of this issue.
The app basically `GET` Azure resources, because both versions exist in Azure, that means we need to be able to `GET` for both.
@jacobbednarz Thank you for the hint. After reviewing issue #173, I feel it is makes more sense to modify the default template to honor the rendered provider name, as is...
One argument is that the default template is almost useless without the support of rendered provider name. E.g. back to my provider, it requires me to use `--provider-name restful`, otherwise,...
Blocking the implementation of https://github.com/magodo/terraform-provider-azurerm/tree/sentinel_alert_rule_ti
@blueww What you described above is the behavior of the `azure-asyncoperation`, as is defined [here](https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/async-api-reference.md#azure-asyncoperation-resource-format), whilst the current RP is using the `location` header, whose flow is defined [here](https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/async-api-reference.md#202-accepted-and-location-headers), that...
I've heard from the Swagger team that the RPC repo is authoritive than the API guideline.
@apparentlymart I've just submit a PR to add the supports for auto-completing the resource addresses for a couple of commands in #29828, right before seeing this issue :sweat_smile: I'd admit...
Just FYI, I've just created a project https://github.com/magodo/hclgrep to allow syntax based grep on HCL2 files. Though `hclgrep` is using a different strategy to query the HCL files as `hclq`...
@sergeylanzman Done.