* chore: upload test results to gcs
* chore: use specific ete variables for gcp upload
* chore: override google_project_number to blank
* chore: use actual env var
* style: fixes flake8 E302 error
* docs: add documentation for new circleci vars
Closes SYNC-4584
* add pytest and script to make for running tests with pytest
* add conftest for pytest path handling
* move store test results to capture integration results
* remove unneeded run_tests and fix warnings about assert_()
Closes SYNC-4612
This reverts commit dc0d571c055741297a77dd47c70b7ef55b552530.
(minus the added RUSTSEC ignore)
utilize the match statement now that we're back on debian
bookworm/python 3.10
Issue SYNC-4259
* feat: Remove support for BrowserID
* mark test only functions as such. I think we can drop MapAndThenTrait for more recent implementations of rust.
Closes: SYNC-3684
* feat: Add metrics, gcp logging to tokenserver scripts
This adds GCP logging JSON output formatting for logs as well as DataDog
style metric reporting.
New Environs:
* `METRIC_API_KEY` - Optional Datadog API key
* `METRIC_APP_KEY` - Optional Datadog APP key
* `METRIC_HOST` - Collector Host address
* `METRIC_PORT` - Collector Host port
This also adds the `--human` arg if you want to use the older, human
readable logs instead.
---------
Co-authored-by: Philip Jenvey <pjenvey@underboss.org>
* bug: validate val names
* not sure why we look for two args when the secret should always be last
* fix names of the range vals to match opts
* normalize `range` to `uid_range` everywhere to prevent possible
problems.
* feat: Allow uid range for purge function
In an attempt to parallelize this script after a very long delay,
specify a range so that multiple scripts can try to process
different ranges of the database.
Closes#1548
* feat: special case purging of users previously migrated to Spanner
don't issue deletes to their current data on syncstorage if their old
"migration records" point to it
and update per RUSTSEC-2024-0336
Closes SYNC-4225
* bug: Add try/except handler for force
This will wrap the force `delete_service_data` with a try/except handler
so as not to prevent the tokenserver record from being removed if the
delete_service_data fails.
* Try/except will capture any errors from trying to call the delete on a
given node, this could fail if the auth or node aren't correct.
* Override will override the attempted node. This will allow us to force
the delete message, even if the original data was copied over and the
node was incorrect.
Note: this commit contains a breaking change. Previously, there was a migration that included two services with static IDs by default, but this commit adds a new migration that removes those two services and adjusts the code to account for the change.
Closes#1144
