Skip to content
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

Update the multicell migration page with eng clarifications #6016

Merged
merged 5 commits into from
Sep 24, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions website/docs/docs/cloud/migration.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,15 +11,15 @@ dbt Labs is in the process of rolling out a new cell-based architecture for dbt

We're scheduling migrations by account. When we're ready to migrate your account, you will receive a banner or email communication with your migration date. If you have not received this communication, then you don't need to take action at this time. dbt Labs will share information about your migration with you, with appropriate advance notice, when applicable to your account.

Your account will be automatically migrated on its scheduled date. However, if you use certain features, you must take action before that date to avoid service disruptions.
Your account will be automatically migrated on or after its scheduled date. However, if you use certain features, you must take action before that date to avoid service disruptions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it's "on or after," can we provide a time frame (within a hour/day/week of the date)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@matthewshaver Right now, no. Accounts are eligible for migration when they're scheduled; however, in the window between scheduling and executing the migration, an account can become ineligible for a number of reasons. How long it takes for them to become eligible again depends on what/how much work is required to support the specific use-case.


## Recommended actions

We highly recommended you take these actions:

- Ensure pending user invitations are accepted or note outstanding invitations. Pending user invitations will be voided during the migration and must be resent after it is complete.
- Commit unsaved changes in the [dbt Cloud IDE](/docs/cloud/dbt-cloud-ide/develop-in-the-cloud). Unsaved changes will be lost during migration.
- Export and download [audit logs](/docs/cloud/manage-access/audit-log) older than 90 days, as they will be lost during migration. If you lose critical logs older than 90 days during the migration, you will have to work with the dbt Labs Customer Support team to recover.
- Ensure pending user invitations are accepted or note outstanding invitations. Pending user invitations may be voided during the migration. You can resend user invitations after the migration is complete.
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
- Commit unsaved changes in the [dbt Cloud IDE](/docs/cloud/dbt-cloud-ide/develop-in-the-cloud). Unsaved changes may be lost during migration.
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
- Export and download [audit logs](/docs/cloud/manage-access/audit-log) older than 90 days, as they may be unavailable from dbt Cloud after the migration is complete. Logs older than 90 days while within the data retention period are not deleted, but you will have to work with the dbt Labs Customer Support team to recover.
eiof marked this conversation as resolved.
Show resolved Hide resolved
eiof marked this conversation as resolved.
Show resolved Hide resolved

## Required actions

Expand Down
Loading