Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tooling: Determining the Cost of a new Service when Importing it #3445

Open
tombuildsstuff opened this issue Dec 5, 2023 · 1 comment
Open

Comments

@tombuildsstuff
Copy link
Contributor

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.

@magodo
Copy link
Contributor

magodo commented Dec 5, 2023

Does this worth to be a separate project so that it can serve a wider scope of scenarios?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants