✅ 39/39 passed, 5 flaky, 2m12s total

Flaky tests:

• 🤪 test_transpiles_informatica_to_sparksql_non_interactive[True] (11.805s)
• 🤪 test_transpile_teradata_sql_non_interactive[False] (12.894s)
• 🤪 test_transpiles_informatica_to_sparksql (13.13s)
• 🤪 test_transpile_teradata_sql (17.314s)
• 🤪 test_transpile_teradata_sql_non_interactive[True] (4.472s)

_{Running from acceptance #2633}

we need a better interface to execute I am not sure if we want to leave it to the developers to always initiate, the workspace and creds. this will lead to inconsistencies sooner or later.

I also would split extracting the "metrics" and persisting them so we need at least two methods extract and persist

I have simplified the usage in the latest push

The primary purpose of this module is to retrieve information from system tables using queries and metrics using APIs, categorised into the following four brackets:

• workspace_extract.py
• monitoring_metrics_extract.py
• dedicated_sqlpool_extract.py
• serverless_sqlpool_extract.py

I don't believe further separating extract and persist makes sense.