Skip to content

feat(ci-lease): S3 fallback for CDK-synth / SAM scenarios#403

Merged
chrisns merged 1 commit into
mainfrom
chore/serialize-and-svc-catalog
May 22, 2026
Merged

feat(ci-lease): S3 fallback for CDK-synth / SAM scenarios#403
chrisns merged 1 commit into
mainfrom
chore/serialize-and-svc-catalog

Conversation

@chrisns
Copy link
Copy Markdown
Member

@chrisns chrisns commented May 22, 2026

Fetch template.yaml from the blueprints bucket when not committed locally. Enables CI for ai-contact-centre, bops-planning, fixmystreet, localgov-drupal, simply-readable, etc.

CDK-synth and SAM-style scenarios don't commit template.yaml (it's
built by deploy-blueprints.yml and uploaded to the hub blueprints
bucket). Without a fallback, scenario-ci.yml fails at 'Template not
found' for those scenarios.

The blueprints bucket already hosts every scenario's latest template
at https://ndx-try-isb-blueprints-568672915267.s3.us-east-1.amazonaws.com/scenarios/<name>/template.yaml
because it's the URL StackSets reference. Anonymous public GET works
for that key path (no IAM auth needed in CI).

ai-contact-centre is the immediate beneficiary: its source template has
relative CodeUri paths that need sam-package to rewrite. The dist/
output (also uploaded to blueprints) has s3:// URIs and is deployable.

Affected scenarios: ai-contact-centre, bops-planning, digital-planning-register,
fixmystreet, localgov-drupal, localgov-ims, minute, paperless-ngx,
planx, simply-readable. Hand-authored scenarios continue to use the
committed template.yaml.
@chrisns chrisns added this pull request to the merge queue May 22, 2026
@chrisns chrisns had a problem deploying to smoke-test-deploy May 22, 2026 09:54 — with GitHub Actions Failure
Merged via the queue into main with commit bc391a6 May 22, 2026
5 of 6 checks passed
@chrisns chrisns deleted the chore/serialize-and-svc-catalog branch May 22, 2026 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant