Skip to content

Commit

Permalink
Add note about non-prod policies not being applied to module repos (#660
Browse files Browse the repository at this point in the history
)
  • Loading branch information
liamg authored Sep 9, 2024
1 parent 11f2106 commit 7d8d9ad
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/infracost_cloud/finops_policies.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,4 +72,6 @@ Some FinOps policies are only applicable to non-production environments, for exa

Infracost supports such policies by allowing you to define filters that identify your production environments (e.g. projects within repos, entire repos or branches that are considered production). You only need to define the filters that match your production environments; Infracost considers everything else as non-production. By default, projects with the words "production", "prod" and "prd" are considered production. You can customize the filters from the Org Settings > Production filters page. Anytime you update this page, you need to go to the Governance > FinOps policies page and click on **Re-run policies** to see the latest failing resources.

Module repositories are skipped during the evaluation of non-production FinOps policies. Instead, the repositories that utilize these modules are checked for those policies.

<img src={useBaseUrl("img/infracost-cloud/finops-policies/production-filters.png")} alt="Production filters can be defined in the Org Settings." />

0 comments on commit 7d8d9ad

Please sign in to comment.