[datadog_compliance_custom_framework] Terraform Provider for Custom Frameworks

[nkonjeti]

Motivation:

We wanted a terraform provider to interact with our Custom Framework APIs. The terraform resources will remain as the source of truth so whenever a resource is updated/created/deleted this will be reflected in the database and UI.

Testing

I built the Terrraform provider locally.

Tested the following:

Creating

Updating

Deleting/Destroying

Changing order of rules

no changes in state so no action taken

Terraform Provider Immutable Fields (Handle And Version)

• if handle or version is changed in a framework this will delete the old framework and create a new one with the new handle and version

• in this example, updating the version to 2 deleted the old framework (version 1) and created a new framework with version 2

• in this example updating the handle and version deleted the old framework with the old handle and version, and created a new framework with the new handle and version

Testing Large Input
Created this Framework: https://dd.datad0g.com/security/compliance/home/custom/my-custom-framework-terraform-3/3.0.0?previousUrl=%2Fsecurity%2Fcompliance%2Fhome&timestamp=1747948011353&live=true
one control with over 200 rule ids (seconds to complete)

Commands:

cd examples/resources/datadog_custom_framework 
terraform init
terraform plan -var="datadog_api_key=<>" -var="datadog_app_key=<>"
terraform apply

also added unit tests!

[Matzoc]

NIT: this is very hard to read in github, could we extract some of the inner loops to their own methods so its more digestible? It also would make it easier to read in the editor

[Matzoc]

Is there a specific reason why we need two validators? the code looks pretty similar between these two (I am probably missing something)