Repository navigation
chore: sync canonical values from catalog-context - #43
Merged
Merged
Conversation
rogiervanstraten
approved these changes
Sep 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated sync of canonical enum values from the latest
catalog-context release,
produced by this repository's own
scripts/sync-catalog-context.mjs.Review the diff before merging: any enum value removed upstream will start
failing validation for entities still using it once this releases.
Note
Low Risk
Schema-only addition of one area enum and tag rule; existing entities are unaffected unless they adopt the new value.
Overview
Adds
banking-ai-opsas a canonical organizational area under the banking domain in the Datadog catalog JSON schemas (catalog-context sync).extensions-defaults.schema.jsonnow allowsextensions.area: banking-ai-opsin the global area enum and in the banking-domainareaconstraint.tags-defaults.schema.jsonadds a matching if/then rule so entities with that area must includearea:banking-ai-opsinmetadata.tags.No enum values were removed in this diff; only the new area is introduced.
Reviewed by Cursor Bugbot for commit e155cfc. Bugbot is set up for automated code reviews on this repo. Configure here.