While the VPN iOS network extension app isn't currently sending main pings with events like the other VPN apps are, it's good to include it for consistency, as the network extension app's main pings are automatically included in the generated mozilla_vpn.main view, and thus are also included in the mozilla_vpn.events_unnested view.
Checklist for reviewer:
[ ] Commits should reference a bug or github issue, if relevant (if a bug is referenced, the pull request should include the bug number in the title).
[ ] If the PR comes from a fork, trigger integration CI tests by running the Push to upstream workflow and provide the <username>:<branch> of the fork as parameter. The parameter will also show up
in the logs of the manual-trigger-required-for-fork CI task together with more detailed instructions.
[ ] If adding a new field to a query, ensure that the schema and dependent downstream schemas have been updated.
[ ] When adding a new derived dataset, ensure that data is not available already (fully or partially) and recommend extending an existing dataset in favor of creating new ones. Data can be available in the bigquery-etl repository, looker-hub or in looker-spoke-default.
For modifications to schemas in restricted namespaces (see CODEOWNERS):
While the VPN iOS network extension app isn't currently sending
main
pings with events like the other VPN apps are, it's good to include it for consistency, as the network extension app'smain
pings are automatically included in the generatedmozilla_vpn.main
view, and thus are also included in themozilla_vpn.events_unnested
view.Checklist for reviewer:
<username>:<branch>
of the fork as parameter. The parameter will also show up in the logs of themanual-trigger-required-for-fork
CI task together with more detailed instructions.For modifications to schemas in restricted namespaces (see
CODEOWNERS
):┆Issue is synchronized with this Jira Task