-
Notifications
You must be signed in to change notification settings - Fork 87
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
Store code migration progress in multiworkspace history log and visualize in dashboard #3112
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comments below
] | ||
return records | ||
|
||
|
||
@pytest.fixture | ||
def catalog_populated( # pylint: disable=too-many-arguments |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Expand name to be more explicit about that it is populated with the data fixture above, e.g. rename to make_catalog_with_test_data(catalog_name: str)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If a fixture is longer than 10 lines, it should be make_
runtime_ctx.direct_filesystem_access_progress.append_inventory_snapshot(dfsas) | ||
del runtime_ctx.direct_filesystem_access_progress | ||
runtime_ctx.used_table_progress.append_inventory_snapshot(used_tables) | ||
del runtime_ctx.used_table_progress | ||
return runtime_ctx.ucx_catalog | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rename dashboard_metadata
to make_dummy_dashboard
(or something alike)
## Changes Follow the more common pattern of expect objects in a class signature. Those objects are passed on from the context. Makes testing more straightforward Breaking down the linked PR below. ### Linked issues Progresses #3045 Breaks up #3112 ### Tests - [x] modified unit tests - [x] modified integration tests
Changes
Store code migration progress in multiworkspace history log and visualize in dashboard
Linked issues
Resolves #3045
Functionality
migration-process
Tests