This adds a script to retrieve client association ping data to respond to access requests. This code is integrated in a bigger, ad-hoc FxA script (see https://bugzilla.mozilla.org/show_bug.cgi?id=1895503), but we want to have it committed here for reference and to track telemetry side of this process. This will come useful when we'll be building automating data access request process.
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):
This adds a script to retrieve client association ping data to respond to access requests. This code is integrated in a bigger, ad-hoc FxA script (see https://bugzilla.mozilla.org/show_bug.cgi?id=1895503), but we want to have it committed here for reference and to track telemetry side of this process. This will come useful when we'll be building automating data access request process.
Checklist for reviewer:
<username>:<branch>of the fork as parameter. The parameter will also show up in the logs of themanual-trigger-required-for-forkCI task together with more detailed instructions.For modifications to schemas in restricted namespaces (see
CODEOWNERS):┆Issue is synchronized with this Jira Task