-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete replicator #2684
Delete replicator #2684
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Don't forget to clean up the SQL stuff and the Firestore write triggers. For deleting the gcloud infrastructure, it should be easy because the replicator is just a single instance and doesn't have anything fancy. If you just click into the VM instances list and terminate the instance, that should be basically it. There's also a Cloud Scheduler cronjob to replay failed writes every minute that you should delete. |
drop trigger replicate_writes on incoming_writes; drop function get_document_table_spec; drop function replicate_writes_process; drop function replicate_writes_process_new; drop function replicate_writes_process_one; drop type table_spec; drop table incoming_writes; drop table tombstones;
looks like someone already stopped the replicator vm |
* delete backend/replicator * move regen-types script to /common and /api * clean up references * Clean up old sql drop trigger replicate_writes on incoming_writes; drop function get_document_table_spec; drop function replicate_writes_process; drop function replicate_writes_process_new; drop function replicate_writes_process_one; drop type table_spec; drop table incoming_writes; drop table tombstones; * yarn regen-types
need to also delete from gcloud and am not sure how