[DOCS-11780] Add API and app key setup guidance to Terraform integration doc

[buraizu]

What does this PR do? What is the motivation?

Fixes DOCS-11780

Adds a note to the Configuration section of the Terraform integration README explaining that api_key and app_key refer to Datadog API and application keys, with a link to create them and guidance to use TF_VAR_* environment variables to avoid hardcoding credentials.

Merge instructions

Merge readiness:

• Ready for merge

Additional notes

References

• DOCS-11780 (Hotjar feedback: users couldn't find where to set up API and app keys on the Terraform integration config page)

[datadog-datadog-prod-us1]

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

Validate repository | Run Validations / Validate     

🛟 This job is unlikely to succeed on retry. Please review your pipeline configuration.

Pull Request #23875 is missing a required QA decision label. Must declare if QA validation is needed for the next Agent release.

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 779b019 | Docs | Datadog PR Page | Give us feedback!}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4e034c9e61

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Declare variables before recommending TF_VAR credentials

For this exact main.tf snippet, setting TF_VAR_datadog_api_key and TF_VAR_datadog_app_key does not make var.datadog_api_key or var.datadog_app_key exist; Terraform only uses TF_VAR_ values for already-declared input variables (see HashiCorp's input-variable docs). Users following the doc as written will still hit undeclared input variable errors during validation/plan/apply unless the example also includes variable blocks for both names, or the guidance instead uses the Datadog provider's supported DD_API_KEY/DD_APP_KEY environment variables.

Useful? React with 👍 / 👎.

[dd-octo-sts]

Validation Report

Validation	Description	Status
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	❌

Run ddev validate all changed --fix to attempt to auto-fix supported validations.

Passed validations (20)

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run