Relationships
#404 dbcluster state schema is missing DBClusterMembers (writer/reader, instance class)
Opened by jentz · 5/21/2026· Shipped 5/22/2026
The @swamp/aws/rds/dbcluster model's persisted state — populated by get / sync via the CloudControl AWS::RDS::DBCluster shape — does not include DBClusterMembers. After sync, the model cannot answer foundational questions about an Aurora cluster:
- Which member is currently the writer?
- What instance class is each member running?
- Which AZ does each member live in?
CloudControl/CFN omits this information by design, but the RDS native DescribeDBClustersCommand returns it. For any workflow operating on live Aurora clusters (failover audits, instance-class migrations, AZ rebalancing), this gap forces consumers to bypass the data model and call AWS directly.
Implementation scope:
- Augment
get/syncto callDescribeDBClustersCommand(in addition to or in place of the CloudControl read), and persist member info into thestateresource. - Schema change: add
DBClusterMembers(withDBInstanceIdentifier,IsClusterWriter,DBClusterParameterGroupStatus,PromotionTier) toStateSchema. Optionally also enrich each entry withDBInstanceClassandAvailabilityZoneby joining againstDescribeDBInstances. - Additive, non-breaking — declare an
upgradesentry for the new version.
Related: the list/discover gap is filed separately. Both share a fix path (direct @aws-sdk/client-rds usage), so they could land together.
Upstream repository: https://github.com/systeminit/swamp-extensions
Environment
- Extension:
@swamp/aws/rds@2026.05.06.1 - swamp:
20260520.150010.0-sha.47868db6 - OS:
darwin(aarch64) - Deno:
2.7.14+19bd3d8 - Shell:
/bin/zsh
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.