fix: use x-cortex-custom-metadata key in environments and ai-spend solutions - #243
Merged
Merged
Conversation
…lutions x-cortex-custom-data is not a recognized Cortex extension. OpenAPI drops unknown x- keys, so these entities imported cleanly while the block was silently discarded and custom() returned null for every key. Changes: - Renamed x-cortex-custom-data to x-cortex-custom-metadata in 24 environments catalog entities - Renamed the same key in the environments GitHub Actions template - Reshaped the 4 ai-spend team budgets from a key/value list to a map, which the parser requires - Corrected the custom data guidance in the building-solutions skill, plus two new error-table rows Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
2 participants
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.
tl;dr - The api expects
x-cortex-custom-metadatanotx-cortex-custom-data.Changes:
x-cortex-custom-datatox-cortex-custom-metadatain 24environmentscatalog entitiesenvironmentsGitHub Actions template that ships into customer reposai-spendteam budgets from akey/valuelist to a map, which the parser requiresbuilding-solutionsskill, plus two new error-table rowsx-cortex-custom-datais not a recognized extension (Parser.kt#L204 definesx-cortex-custom-metadataas the only one). OpenAPI drops unknownx-keys, so these imported clean and the data was discarded. Impact was the marquee demo of each solution: the CVE exposure query inenvironments, and the Silver/Gold budget rules inai-spend.Not changed: the
jq(..., ". | tonumber")casts inai-spend-scorecardstill work, since jqtonumberaccepts a number.Verified statically: parser constant, the
!is Mapguard that breaks the list shape, and ayqparse of all 30 files. Not verified against a live tenant.Session: b0fa4a64 · Worktree: cli/custom-metadata-key
🤖 Generated with Claude Code