Skip to content

#253 step 7: throw on unset MMGIS_ENVIRONMENT and drop the legacy recipe JSONs - #284

Open
CarsonDavis wants to merge 2 commits into
developmentfrom
chore/253-step7-drop-legacy-fallback
Open

#253 step 7: throw on unset MMGIS_ENVIRONMENT and drop the legacy recipe JSONs#284
CarsonDavis wants to merge 2 commits into
developmentfrom
chore/253-step7-drop-legacy-fallback

Conversation

@CarsonDavis

Copy link
Copy Markdown
Collaborator

The legacy staging environment is fully torn down, so its two lingering supports come out.

  • MMGIS_ENVIRONMENT unset now throws instead of falling back. stackNamePrefix() returned the shared legacy prefix mmgis-dashboard- when the variable was unset — a convenience that only the (now-deleted) hand-built staging environment relied on. It now throws, matching the existing regex/length guards. Safe for full/local mode: the publish/dashboard path only mounts under isLean(), where Terraform always injects the variable.
  • Delete the legacy recipe JSONs. The 7 infrastructure/{ecs,iam}/*.json snippets mirrored the hand-built environment and no longer describe anything real. Removed, with their coupled tests and the README provenance/placeholder sections. The 3 live-artifact templates (cloudfront-*, s3-asset-bucket.json) stay.

Closes the code-side criterion of #253's teardown. 966 tests green.

The Terraform module injects MMGIS_ENVIRONMENT into every lean runtime and
full mode never reaches this code, so an unset value has no legitimate case.
Drop DEFAULT_STACK_NAME_PREFIX and the unset/empty fallback in stackNamePrefix()
and throw a loud error instead, matching the existing validation guards.
The legacy staging environment is torn down, so the ecs/ and iam/ recipe JSONs
it justified are dead. Remove the seven task and role JSONs, the infrastructure
spec tests that read them, and the README regions that documented them, keeping
cloudfront-admin.json, cloudfront-function.js, and s3-asset-bucket.json.
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