A Terraform provider, Oracle Cloud and New Relic, and findings you choose

This month PruneOps fits better into the way you already work: you configure it from code, it covers two more providers, and it only flags what matters to you.

PruneOps as code: our own Terraform provider

• Configure your organization from Terraform, reviewed and versioned like the rest of your infrastructure: cloud accounts, Kubernetes clusters, what gets inventoried and tracked, Terraform states, allocation groups, budgets, anomaly alerts and findings.
• To get started, create an API token under Organization → Integrations → API Tokens with Read or Write per area, and declare the provider:

terraform {
  required_providers {
    pruneops = {
      source = "registry.pruneops.run/pruneops/pruneops"
    }
  }
}

Full guide at www.pruneops.run/docs/integrations/terraform-provider.

Providers

• Oracle Cloud (new): inventory of Compute, storage, OKE, Autonomous Database and networking, with the real billed cost imported daily.
• New Relic (new): users, ingested data and synthetic monitors, with spend estimated from usage and findings for idle seats and unread data.
• OVH (expanded): now also managed databases, network, snapshots, Kubernetes and registry, with the cost of each resource checked against OVH's official invoice.

Findings: you decide what gets flagged

• Not every finding applies to every team. Under Organization Settings → Findings, owners and admins can switch off the ones that don't fit, filtering by provider, severity and type.
• A disabled finding stops producing recommendations and no longer counts in the scores. Recommendations you already dismissed or applied stay as history.

We'll keep moving forward and improving, with what you tell us as the guide.