fix(localgov-drupal): sync Aurora MaxCapacity 8 into template.yaml#187
Merged
Conversation
Follow-up to #186. The CDK source raised serverlessV2MaxCapacity from 2 to 8 ACU so the first-boot 33-module install does not peg the cluster, but the hand-edited template.yaml was not regenerated (deploy-blueprints workflow has been failing on a pre-existing jest types issue since 2026-04-16, so the synth-and-write step does not run). Without this, new sandbox sessions provisioned from the StackSet still get MaxCapacity: 2 and the install takes ~9 minutes instead of ~3. This aligns the committed template with the StackSet template I updated directly in us-west-2 earlier today and with what the CDK source expresses.
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
Follow-up to #186. The CDK source (
database.ts) raisedserverlessV2MaxCapacityfrom 2 to 8 ACU so the first-boot 33-module install doesn't peg the cluster for ~9 min, buttemplate.yamlwasn't regenerated because thedeploy-blueprintsworkflow has been failing since 2026-04-16 on a pre-existing jest types error in the localgov-drupal CDK tests.Without this, new sandbox sessions provisioned from the StackSet still get
MaxCapacity: 2.Already applied out-of-band directly to the hub StackSet in us-west-2 (
ndx-try-localgov-drupal) and tos3://ndx-try-isb-blueprints-568672915267/scenarios/localgov-drupal/template.yaml. This commit makes the repo the source of truth again.Test plan
MaxCapacity: 8live in the hub StackSet (see earlier work today)deploy-blueprintsis unblocked (separate PR for jest types), it will regeneratetemplate.yamlfrom CDK; this edit is compatible with that output.