32 lines
1.2 KiB
MySQL
32 lines
1.2 KiB
MySQL
|
/*
|
||
|
|
Macro: get_new_dash_migration_phases_configuration
|
||
|
|
|
||
|
|
Provides a general configuration for the different phases of the
|
||
|
|
New Dash migration. Each phase is identifiable via a phase_name,
|
||
|
|
that is the "expected display" for users. The assumption is that
|
||
|
|
each user migration is identified via claim_type. Lastly, we
|
||
|
|
apply here a hardcode of when the deployment was carried out.
|
||
|
|
|
||
|
|
Important note: if a user migrates once a phase has started, we
|
||
|
|
will not be able to tell when that happened. However, it is likely
|
||
|
|
that other indicators will provide an estimate. For example:
|
||
|
|
|
||
|
|
The migration A happens on 1st July 2024.
|
||
|
|
User A is migrated on 1st July 2024 (as expected)
|
||
|
|
User B is migrated on 10th July 2024 (not expected)
|
||
|
|
|
||
|
|
It is likely that User B won't have Bookings from new dash
|
||
|
|
until it's migrated. So this migration date should be considered
|
||
|
|
as a hard, lower-limit of dates.
|
||
|
|
*/
|
||
|
|
|
||
|
|
{% macro get_new_dash_migration_phases_config() %}
|
||
|
|
{% set migration_phases = [
|
||
|
|
{
|
||
|
|
'phase_name': 'MVP',
|
||
|
|
'claim_type': 'KYGMVP',
|
||
|
|
'deployment_date': '2024-07-30'
|
||
|
|
}
|
||
|
|
] %}
|
||
|
|
{{ return(migration_phases) }}
|
||
|
|
{% endmacro %}
|