Closed mnlumi closed 11 months ago
I believe there are two issues across the failing examples:
azure-native:insights:Component (ai): error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="Cannot set LogAnalytics as IngestionMode on current api-version" InnerError={"trace":["System.ArgumentException"]}
Sounds like a legitimate issue that needs to be fixed.
azure:lb:Rule (lbnatrule-http): error: deleting urn:pulumi:p-it-fv-az1230--classic-az-c4ac5288::azure-ts-vm-scaleset::azure:lb/rule:Rule::lbnatrule-http: 1 error occurred:
- waiting for completion of Load Balancer "lba38cbe08" (Resource Group "vmss-rg5eeda2c8"): Code="NotFound" Message="Resource /subscriptions/***/resourceGroups//providers/Microsoft.Compute/tenants/38DF66CC-83A1-4EDF-A462-24DA3E8114E1 not found." Details=[]
Less clear what is happening here. Are you able to reproduce this issue locally in the TestAccAzureTsVmScaleset example?
WRT to the first failure @lukehoban identified (the error with azure-native:insights:Component
, it looks like we just need to specify the ingestion mode. Unfortunately, the API reference page (https://www.pulumi.com/registry/packages/azure-native/api-docs/insights/component/) doesn't provide any details on ingestion mode (that supporting type is blank/missing details).
Opened https://github.com/pulumi/registry/issues/2966 for the api-docs.
@cnunciato @scottslowe All of the tests are passing 🎉
@cnunciato Would you be able review these updates? I've taken in the latest fixes for tests, there are still a few failing.