Update the multicell migration page with eng clarifications #6016
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
| @@ -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. | |||
There was a problem hiding this comment.
If it's "on or after," can we provide a time frame (within a hour/day/week of the date)?
There was a problem hiding this comment.
@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.
| @@ -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. | |||
There was a problem hiding this comment.
@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.
What are you changing in this pull request and why?
We recently updated the migration checklist in #6002. Engineering has reviewed the changes, and recommends clarifying some points in attempt to be more accurate and reassuring to our customers.
Checklist