c8f4d2be70
# Description First step towards reporting New Dash is to be able within DWH to know which hosts have been migrated. In order to do so, and anticipating that there's going to be new phases in the future, I've created a `int_core__user_migration` model that reads from a configuration macro `get_new_dash_migration_phases_config` that will allow semi-automatic user retrieval in the future. This avoids nasty hardcoding within the model itself. The information of whether a user is migrated, in which phase and when the phase was deployed is available at user level in the `int_core__user_host` table. # Checklist - [X] The edited models and dependants run properly with production data. - [X] The edited models are sufficiently documented. - [X] The edited models contain PK tests, and I've ran and passed them. - [X] I have checked for DRY opportunities with other models and docs. - [X] I've picked the right materialization for the affected models. **-> I selected a view for this model since I don't believe we should materialse this data other than the user host table** # Other - [ ] Check if a full-refresh is required after this PR is merged. Related work items: #19570 |
||
|---|---|---|
| .. | ||
| tests | ||
| .gitkeep | ||
| business_kpis_configuration.sql | ||
| calculate_safe_relative_increment.sql | ||
| generate_schema_name.sql | ||
| generate_stripe_sources_unioned_select.sql | ||
| is_date_before_previous_month.sql | ||
| user_migration_configuration.sql | ||