Support for Schema v3 in datadog_service_definition_yaml

[JeanFred]

What resources or data sources are affected?

datadog_service_definition_yaml

Feature Request

Schema Version 3 is in beta (https://docs.datadoghq.com/service_catalog/adding_metadata/#metadata-schema-v30-beta) and it is documented on Github https://github.com/DataDog/schema/tree/main/service-catalog/v3

References

No response

[bbrunodiad]

Any update?

[samcrudge]

Attempted to resolve this with #3141

[Nexyro]

Hi @samcrudge and @JeanFred ,

I think what you are looking for is datadog_software_catalog. datadog_service_definition_yaml is only keep for v2* Schema Definition

ref : https://registry.terraform.io/providers/DataDog/datadog/3.69.0/docs/resources/software_catalog`

[samcrudge]

Hi @samcrudge and @JeanFred ,

I think what you are looking for is datadog_software_catalog. datadog_service_definition_yaml is only keep for v2* Schema Definition

ref : https://registry.terraform.io/providers/DataDog/datadog/3.69.0/docs/resources/software_catalog`

Thanks man,
My implementation in the PR:

Use datadog_software_catalog for v3 schemas

• Modern resource with apiVersion: v3 and kind: service|datastore|queue|system syntax
• Full Software Catalog API support

Keep datadog_service_definition_yaml for v2.x legacy

Backward compatibility for existing schema-version: v2.x definitions

• Also supports v3 for gradual migration
  The branch includes proper validation, tests, and examples for both approaches.

Thanks @Nexyro for the registry docs reference, good distinction.