Repository navigation
docs(kiro): narrow the validate-template prohibition to provider-owned constraints - #4932
Merged
kddejong merged 1 commit intoOct 26, 2026
Conversation
…d constraints validate-template invokes no resource provider, so it cannot establish a property value, limit, enum or cross-property rule. That reasoning does not extend to template-level structure, which the control plane itself parses and which validate-template is therefore testing directly. Recorded us-east-1, 2026-10-26: a parameter of Type: List<AWS::SSM::Parameter::Value<String>> draws the identical "Template format error: List of AWS::SSM::Parameter::Value is not supported." from validate-template and from create-stack, and no stack is created. Raised by issue aws-cloudformation#4854, where the reporter cited validate-template for a parameter type and our own context said that was not evidence. The deployment-first evidence ranking from aws-cloudformation#4867 is unchanged.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4932 +/- ##
==========================================
- Coverage 94.70% 94.68% -0.03%
==========================================
Files 441 441
Lines 16058 16067 +9
Branches 3113 3116 +3
==========================================
+ Hits 15208 15213 +5
- Misses 468 470 +2
- Partials 382 384 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
Problem
.kiro/tells agents thataws cloudformation validate-templateis not evidence for a constraint. For a property-level constraint that is right:validate-templateinvokes no resource provider, so it cannot establish a property value, limit, enum or cross-property rule.The wording over-reached. It also covered template-level structure, which the CloudFormation control plane parses itself — exactly what
validate-templatedoes check. For that class,validate-templatereturns the same errorCreateStackdoes, and it is free and leaves nothing behind.This surfaced on #4854. The reporter cited
validate-templatefor a parameter type, our own agent context said that was not evidence, and the reporter was right. These files are read on every agent session, so the next agent would have dismissed correct evidence the same way.Evidence
Recorded us-east-1, 2026-10-26, on this template:
Identical error code and message from both APIs, and no stack created. A parameter type is parsed by the control plane, not by a resource provider, which is why the two agree here and do not agree on a property constraint.
What changed
Three files, one paragraph each, kept short because they are session context.
.kiro/context/verification.md— reframed from "is NOT evidence" to "is scoped to the control plane", with both halves stated and the measured parameter-type case recorded..kiro/context/false-positives.md(doctrine item 4) — same distinction, compressed; the measured case is not repeated here..kiro/steering/rule-development.md(Validation Approach step 1) — the one-clause version now says "for a property constraint" instead of forbidding the tool outright."Never cite it as a probe" is kept for the property case.
Not changed
validate-templateis not promoted into the ranked list.Verification
The
dependencies (ubuntu-latest, 3.10)job fails on a pip-audit CVE infilelock, pre-existing onmainand unrelated to this change.