Repository navigation
feat(bb-database): SQL in-place deploy - #1651
Merged
Merged
Conversation
…ase with the same id A Database that owns its Aurora DSQL cluster declares the cluster under the logical id <fullId>DsqlCluster, which DistributedDatabase of @aws-blocks/bb-distributed-data used. CloudFormation then sees one resource, and the deploy keeps the cluster and its rows. A shared DatabaseCluster keeps the logical id of its construct path. - Two owned blocks whose ids give the same logical id fail at synth with an error that names both. - A test on PGlite reads the _migrations table of the earlier block: an applied file does not run again, and a new file is recorded. - test-apps/comprehensive: test:upgrade-distributed-database deploys the 0.3.0 release, upgrades the stack to this checkout, and compares the cluster identifier and the rows. Its API accepts signed calls only. - docs/guides/upgrading-older-apps.md has the steps.
pranavosu
temporarily deployed
to
agent-bench
November 18, 2026 23:46 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 18, 2026 23:46 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 18, 2026 23:46 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 18, 2026 23:46 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 18, 2026 23:46 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 18, 2026 23:46 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 18, 2026 23:46 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 18, 2026 23:46 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 18, 2026 23:46 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 19, 2026 06:59 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 19, 2026 06:59 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 19, 2026 06:59 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 19, 2026 06:59 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 19, 2026 06:59 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 19, 2026 06:59 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 19, 2026 06:59 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 19, 2026 06:59 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 19, 2026 06:59 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 19, 2026 06:59 — with
GitHub Actions
Inactive
pranavosu
temporarily deployed
to
agent-bench
November 19, 2026 07:50 — with
GitHub Actions
Inactive
3 tasks done
This branch was previously deployed
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
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
An app that deployed a SQL block of an earlier release keeps its database when it moves to
Databaseof@aws-blocks/bb-database.Changes
DistributedDatabase: aDatabasethat owns its Aurora DSQL cluster declares the cluster under the logical id of the earlier block,<fullId>DsqlCluster. The same id gives the same cluster.Databaseofbb-data:LegacyDatabaseClusterdeclares the Aurora cluster, the secret and the VPC of release 0.5.0 under the same logical ids. Its infrastructure code is that release's, and is frozen. ADatabasewith a new id runs on it.DatabaseCluster.fromExisting({ dataApi })reaches an Aurora PostgreSQL cluster through the RDS Data API, with no connection and no VPC wiring. The legacy cluster uses the same engine.npm run test:upgrade-sql-blocks -- --scenario dsql|auroradeploys the release, upgrades the stack, and compares the resources and the rows.docs/guides/upgrading-older-apps.md.Compatibility
@aws-blocks/bb-databaseis not published. A stack that was deployed frommainwith an owned DSQL cluster gets a different logical id, so its next deploy replaces that cluster. Maintainers, please confirm.asUser()is an error on aLegacyDatabaseCluster: the owner of the tables runs the statements there, so row-level policies apply throughasRole().@aws-sdk/client-rds-data.Tests
bb-database372,blocks630 and 52. All pass.main.aurora13 of 13 on the final code.dsql12 of 12, before the harness got its scenarios.comprehensive.