beginCreateAndWait method is returning operation status instead of tracked resource (@azure/arm-workloads)
See original GitHub issue- Package Name:
@azure/arm-workloads
- Package Version:
1.0.0-beta.1
- Operating system:
Windows
- nodejs
- version:
16.8.0
- version:
Describe the bug
While monitor creation beginCreateAndWait
function has data type Monitor
const monitor = await client.monitors.beginCreateAndWait(
resourceGroup,
monitorName,
createMonitorPayload as Monitor
);
But response is long running operation and monitor properties are null
To Reproduce Steps to reproduce the behavior:
- Create any tracked resource using
@azure/arm-workloads
package
Expected behavior
Method should return Monitor
object. So basically, id
would be \subscriptions\<subscriptionId>\resourceGroups\<rgname>\providers\Microsoft.Workloads\monitors
, name
should be resource name not operation status name
Screenshots Pasted above
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Issues - GitHub
hashicorp / terraform-provider-azurerm Public ... Status=400 Code="NotSupported" Message="Operation \"purge\" is not enabled for this vault." #10132.
Read more >Troubleshoot common problems when using Terraform on Azure
In this article. HashiCorp Terraform specific support channels; Unable to list provider registration status; Error acquiring the state lock ...
Read more >azurerm_storage_account | Resources | hashicorp/azurerm
resource_group_name - (Required) The name of the resource group in which to ... from Storage to StorageV2 keeping the existing storage account in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@MaryGao @kazrael2119 New package resolves the issue.
Hi @hirenchalodiya1 , I fixed this issue and regenerated this package. You can use this package to verify whether your problem is solved. Here is the package: azure-arm-workloads-1.0.0-beta.2.zip