fix: set application/yaml content-type for autonomous_work ask-body commands - #205
Merged
Conversation
…ommands The 7 YAML ask-body create/update commands (work_class, work_trigger, capability, risk_evaluator, member, member_template, software_component) declared file_body: required but no content_type, so the file was sent as application/json and adlc-service rejected it. Also corrects team/ content_source_connector set_default help text: those are plain JSON bodies, not YAML ask-bodies. Co-Authored-By: Claude Sonnet 5 <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
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.
Summary
work_class,work_trigger,capability,risk_evaluator,member,member_template,software_component) declaredfile_body: requiredbut nocontent_type, so the file was sent asapplication/jsonand adlc-service rejected it. Addedcontent_type: application/yamlto each.teamandcontent_source_connector set_defaultcommand help text — those are plain JSON bodies, not YAML ask-bodies (same root cause identified in fix: correct autonomous_work YAML ask-body content-type and Team schema mcp-server#932).Test plan
contracts/schemas/v1/*.schema.jsonfor the affected resources