ci: add AWS host conformance gate#6
Merged
Merged
Conversation
Exercise the legacy IaC module plugin against both declared minimum and current Workflow engine releases.
intel352
force-pushed
the
codex/iac-host-conformance
branch
from
a160844 to
ca3d61e
Compare
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
iac.providermodule discovery plus strict module contract registry exposureScope note
AWS still ships as a legacy
sdk.Servemodule plugin, not a strict-cutoversdk.ServeIaCPluginprovider. This PR intentionally validates the shipped boundary. A future AWS typed-provider migration should add a DO-styleIaCProviderRequiredRPC conformance gate.Verification
GOWORK=off go test ./...GOWORK=off go vet ./..../scripts/workflow-iac-host-conformance.sh v0.19.0 min./scripts/workflow-iac-host-conformance.sh v0.51.2 currentAntagonistic review: initial review requested clarity on the legacy-vs-typed boundary; follow-up review verdict was SHIP-IT after scoping the gate as legacy module-plugin conformance.