Description
The service-catalog/v3/ directory is missing a frontend.schema.json file, even though kind: frontend is a supported native entity type.
Evidence
Docs confirm frontend is a native entity:
The Native Entities documentation lists six native entity types: service, system, api, datastore, queue, and frontend.
API accepts frontend entities:
POST /api/v2/catalog/entity with apiVersion: v3 and kind: frontend succeeds and returns a valid entity with an ID.
Schema repo is missing it:
The v3 directory contains schema files for service, system, api, application, datastore, queue, and custom, but no frontend.schema.json.
Current v3 schema files
api.schema.json
application.schema.json
custom.schema.json
datastore.schema.json
entity.schema.json
metadata.schema.json
queue.schema.json
service.schema.json
system.schema.json
Impact
Anyone validating their service.datadog.yaml files against the schemas in this repo will incorrectly conclude that kind: frontend is not a valid entity type, even though it works in production. This also means local validation tooling and CI checks that reference these schemas will reject valid frontend definitions.
Expected
A frontend.schema.json file should exist in service-catalog/v3/ alongside the other native entity schemas, defining the valid spec properties for frontend entities (e.g., type, lifecycle, tier, componentOf, dependsOn). Based on API validation, spec.languages is not a valid property on frontend entities (unlike service entities), so the schema should reflect that constraint.
Description
The
service-catalog/v3/directory is missing afrontend.schema.jsonfile, even thoughkind: frontendis a supported native entity type.Evidence
Docs confirm frontend is a native entity:
The Native Entities documentation lists six native entity types: service, system, api, datastore, queue, and frontend.
API accepts frontend entities:
POST /api/v2/catalog/entitywithapiVersion: v3andkind: frontendsucceeds and returns a valid entity with an ID.Schema repo is missing it:
The v3 directory contains schema files for
service,system,api,application,datastore,queue, andcustom, but nofrontend.schema.json.Current v3 schema files
Impact
Anyone validating their
service.datadog.yamlfiles against the schemas in this repo will incorrectly conclude thatkind: frontendis not a valid entity type, even though it works in production. This also means local validation tooling and CI checks that reference these schemas will reject valid frontend definitions.Expected
A
frontend.schema.jsonfile should exist inservice-catalog/v3/alongside the other native entity schemas, defining the validspecproperties for frontend entities (e.g.,type,lifecycle,tier,componentOf,dependsOn). Based on API validation,spec.languagesis not a valid property on frontend entities (unlike service entities), so the schema should reflect that constraint.