ci: add wrapper output-forwarding gate (prevent v0.3.x-class regressions)#45
Open
dmchaledev wants to merge 1 commit into
Open
ci: add wrapper output-forwarding gate (prevent v0.3.x-class regressions)#45dmchaledev wants to merge 1 commit into
dmchaledev wants to merge 1 commit into
Conversation
…sions The existing wrapper-forwarding job checked that wrappers expose every variable from their core module, but had no equivalent check for outputs. The v0.3.x regression (post_patch_ssm_document_name, redis_endpoint, redis_mode silently missing from HA wrappers) slipped through exactly because of this gap. Add a "Diff wrapper outputs against their core modules" step in the same job. It mirrors the variable-diff logic: for each of the 12 wrapper/core pairs, compare output names with comm -23 and fail if the wrapper is missing any output the core declares. No new dependencies — pure shell. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JiqETiysB7AxP9ypY1LetL
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
The existing
wrapper-forwardingCI job enforces that every wrapper module (sat-*,asm-*) exposes the same variable surface as its core module. There was no equivalent check for outputs.The v0.3.x regression —
post_patch_ssm_document_name,redis_endpoint, andredis_modesilently missing from all HA wrapperoutputs.tffiles — slipped through CI exactly because of this gap. Operators hit aterraform output redis_endpointerror at runtime, not at PR merge time.Change
Add one new step — "Diff wrapper outputs against their core modules" — to the existing
wrapper-forwardingjob in.github/workflows/ci.yml.The logic mirrors the variable-diff step directly above it:
All 12 wrapper/core pairs are covered. If the core module adds a new output and any wrapper's
outputs.tfdoesn't re-export it, CI fails with a named list of missing outputs.Why this is the right level
terraform testfor wrappers). That's the right long-term fix; this gate catches the specific class of omission immediately and cheaply.Test plan
wrapper-forwardingjob passes on this branch (all 12 wrappers already re-export full output surface after the v0.3.x fix)outputblock from a wrapperoutputs.tfand confirm the step errors with the missing output name listedterraform validateandtflintunaffected (onlyci.ymlchanged)Generated by Claude Code