You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -72,20 +57,7 @@ In order to unify the workflow triggering mechanism, we use [a Cloud Run functio
72
57
2. Make adjustments to the dataform configuration files and manually run a workflow to verify.
73
58
3. Push all your changes to a dev branch & open a PR with the link to the BigQuery artifacts generated in the test workflow.
74
59
75
-
### Dataform development workspace hints
76
-
77
-
1. In workflow settings vars:
78
-
79
-
- set `env_name: dev` to process sampled data in dev workspace.
80
-
- change `today` variable to a month in the past. May be helpful for testing pipelines based on `chrome-ux-report` data.
81
-
82
-
2.`definitions/extra/test_env.sqlx` script helps to setup the tables required to run pipelines when in dev workspace. It's disabled by default.
83
-
84
-
### Error Monitoring
85
-
86
-
The issues within the pipeline are being tracked using the following alerts:
87
-
88
-
1. the event trigger processing fails - [Dataform Trigger Function Error](https://console.cloud.google.com/monitoring/alerting/policies/570799173843203905?authuser=7&project=httparchive)
89
-
2. a job in the workflow fails - "[Dataform Workflow Invocation Failed](https://console.cloud.google.com/monitoring/alerting/policies/16526940745374967367?authuser=7&project=httparchive)
60
+
#### Workspace hints
90
61
91
-
Error notifications are sent to [#10x-infra](https://httparchive.slack.com/archives/C030V4WAVL3) Slack channel.
62
+
1. In `workflow_settings.yaml` set `env_name: dev` to process sampled data.
63
+
2. In `includes/constants.js` set `today` or other variables to a custome value.
0 commit comments