marketplace: container-image (ECS/Fargate) delivery option template#237
Merged
Conversation
Adds an EcrDeliveryOptionDetails delivery option alongside the live Helm/EKS option, reusing the same re-hosted Marketplace-ECR image (one artifact, two delivery options). Reaches ECS / Fargate / docker-pull buyers with no new build; additive change that does not touch the Helm option. - specifications/marketplace-container-image-delivery.md (+ .acceptance.md): ACTIVE integration-mapping spec pinning the same-image invariant, behavioral parity, and the non-Helm deployment contract (durable snapshot storage on Fargate since the task filesystem is ephemeral, non-root, config + secret injection). - docs/marketplace/catalog-api/04-add-container-image-delivery.json: the additive AddDeliveryOptions change-set template (CompatibleServices ["ECS"]). - scripts/marketplace-changeset.sh: preflight guard rejecting unsupported CompatibleServices values before start-change-set; usage header for step 04. - docs/marketplace/catalog-api/README.md: reach-expansion delivery-option table. Live submission + representative-environment smoke (TC-CID-05) remain a gated operator step, so this does not close the issue. Refs #234, #233
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.
Part of #233 (Marketplace reach expansion). Adds the second delivery option to the live Elevarq Signals listing: an
EcrDeliveryOptionDetailsoption for Amazon ECS / AWS Fargate /docker pull, alongside the existing Helm/EKS option. It reuses the same already-re-hosted Marketplace-ECR image — no new build, no new artifact, Helm option untouched.What's here (in-repo artifacts)
specifications/marketplace-container-image-delivery.md(ACTIVE) +.acceptance.md— integration-mapping spec. Load-bearing decisions:docs/marketplace/catalog-api/04-add-container-image-delivery.json— additiveAddDeliveryOptionschange-set template,CompatibleServices: ["ECS"](Fargate is an ECS launch type).scripts/marketplace-changeset.sh— new preflight guard rejecting unsupportedCompatibleServicesvalues beforestart-change-set(AWS only validates this after submit, burning a change-set); usage header for step 04.docs/marketplace/catalog-api/README.md— reach-expansion delivery-option table.Decisions (confirmed)
CompatibleServices: ["ECS"]only — notECS-Anywhere(unvalidated for the RDS/Aurora IAM path; claim only what we've verified).Validation
shellcheck scripts/marketplace-changeset.sh— clean (default severity).${...}, 0 non-ASCII; CompatibleServices guard passes valid input and catches an injected bad value.trivy fs --scanners secret .— clean.Not done by merging this
The actual AWS
AddDeliveryOptionssubmission + the live ECS/Fargate smoke are a gated operator step (needs the product Limited/Public, triggers the ~40-min ingestion scan, one review round). So this usesRefs #234and does not auto-close it.Refs #234, #233