Stop Exporting Tables to Redshift via DMS that DBT is accessing via Zero ETL - #74627
Open
sureshc wants to merge 1 commit into
Open
Stop Exporting Tables to Redshift via DMS that DBT is accessing via Zero ETL#74627sureshc wants to merge 1 commit into
sureshc wants to merge 1 commit into
Conversation
…ero ETL. Co-Authored-By: Claude <claude@users.noreply.github.com>
|
[WARN: DMS Config Modified] This PR modifies the |
Contributor
Author
|
I backed up the configuration of the Replication Tasks that are deleted by this change (using AWS CLI commands) and then executed the deployment: code-dot-org $ bundle exec rake stack:data:start RAILS_ENV=production ADMIN=true
Finished stack:data:environment (less than a minute)
Pending update for stack `DATA-production`:
Modify DMSCronPii [AWS::DMS::ReplicationTask] Properties Replacement: Conditional (TableMappings)
Remove DMSCronUserHierarchyPii [AWS::DMS::ReplicationTask]
Remove DMSCronUserHierarchy [AWS::DMS::ReplicationTask]
Modify DMSCron [AWS::DMS::ReplicationTask] Properties Replacement: Conditional (TableMappings)
Proceed? [y/n]
y
Stack update requested, waiting for provisioning to complete...
.2026-08-13 22:13:36 UTC- DMSCron [UPDATE_IN_PROGRESS]
2026-08-13 22:13:36 UTC- DMSCronPii [UPDATE_IN_PROGRESS]
........2026-08-13 22:14:21 UTC- DMSCronPii [UPDATE_COMPLETE]
2026-08-13 22:14:21 UTC- DMSCron [UPDATE_COMPLETE]
.2026-08-13 22:14:23 UTC- DATA-production [UPDATE_COMPLETE_CLEANUP_IN_PROGRESS]
2026-08-13 22:14:23 UTC- DATA-production [UPDATE_COMPLETE_CLEANUP_IN_PROGRESS]
Stack update complete. |
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.
@code-dot-org/red-team has updated most
dbtmodels to read data from Zero ETL Materialized Views. Stop exporting tables from MySQL to Redshift via Database Migration Service (DMS) if there are no longer anydbtmodels that reference the DMS tables in Redshift.RED Team - The following tables are now exporting to Redshift via Zero ETL and ready for you to cutover in
dbtto use the Materialized Views:HoneyBadger errors show that
bin/cron/redshift_rollupshas been failing for more than a year, so I'm ignoring the tables it's dependent on for determining whether or not to continue exporting them via DMS.Testing story
Deployment notes
Privacy and security