You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Different Resources within Azure have different costs - some free (Resource Groups), some billed by the minute/hour (e.g. Virtual Machines, Network Interfaces, Application Gateways) and some billed monthly/yearly (e.g. Dynatrace).
When a PR is opened adding a new Service into Pandora, we should request the pricing model for/look to determine the pricing model for the associated service so we can determine the billing model - and whether it makes sense for this Service to be imported/supported.
This would allow us to catch scenarios such as hashicorp/terraform-provider-azurerm#23800 where the billing model ($25,000/year/resource at a minimum for Dynatrace) makes running any acceptance tests cost-prohibitive - and thus requires further investigation to determine if the Resource should be supported in Terraform at all.
The text was updated successfully, but these errors were encountered:
Different Resources within Azure have different costs - some free (Resource Groups), some billed by the minute/hour (e.g. Virtual Machines, Network Interfaces, Application Gateways) and some billed monthly/yearly (e.g. Dynatrace).
When a PR is opened adding a new Service into Pandora, we should request the pricing model for/look to determine the pricing model for the associated service so we can determine the billing model - and whether it makes sense for this Service to be imported/supported.
This would allow us to catch scenarios such as hashicorp/terraform-provider-azurerm#23800 where the billing model ($25,000/year/resource at a minimum for Dynatrace) makes running any acceptance tests cost-prohibitive - and thus requires further investigation to determine if the Resource should be supported in Terraform at all.
The text was updated successfully, but these errors were encountered: