-
Notifications
You must be signed in to change notification settings - Fork 99
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
Fix conditional execution on populate schema action #998
Conversation
1d84218
to
6531931
Compare
Workflow dispatch run: https://github.com/dbt-labs/metricflow/actions/runs/7662451871 Note the workflow dispatch run was canceled when I deployed the engine tests, but that deployment confirmed that the reload tests updated here were appropriately skipped when I added the engine tests label. |
The populate persistent source schema GitHub action has a workflow_dispatch trigger, but when you attempt to use it all actions are immediately skipped. This makes the changes necessary to enable the workflow_dispatch trigger to execute the tasks in this workflow.
b5a6630
to
cb73c0c
Compare
Current dependencies on/for this PR:
This stack of pull requests is managed by Graphite. |
cb73c0c
to
6d0062e
Compare
Databricks and BigQuery are super slow on data load, which leaves us wondering if they're doing anything. Without a log-cli-level set the action logs just sit for a good 3 minutes. This adds log-cli-level info to the command in order to provide some more detail on what the actions are doing, which will also be helpful if something should fail.
6d0062e
to
163b3c8
Compare
The populate persistent source schema GitHub action has a
workflow_dispatch trigger, but when you attempt to use it all
actions are immediately skipped.
This makes the changes necessary to enable the workflow_dispatch
trigger to execute the tasks in this workflow.