7ed261fc52
Adds infrastructure and client for interaction with GCP object storage services. Note: this is just a client object usable for creating, listing, deleting and up/downloading of objects to/from said storage service. It makes no attempt at actually inserting it into the sstable storage flow. That can come later. This PR breaks out GCP auth and some general REST call functionality into shared routines. Not all code is 100% reused, but at least some. Test is added, though could be more comprehensive (feel free to suggest a test vector). Test can run in either local mock server mode (default), or against actual GCP. See `test/boost/gcp_object_storage_test.cc` for explanation on the config environment vars. Default is to run the test against a temporary docker deamon. Closes scylladb/scylladb#24629 * github.com:scylladb/scylladb: test::boost::gcp_object_storage_test: Initial unit tests for GCP obj storage proc-utils: Re-export waiting types from seastar proc-utils: Inherit environment from current process utils::gcp::object_storage: Add client for GCP object storage utils::http: Add optional external credentials to dns_connection_factory init utils::rest: Break out request wrapper and send logic encryption::gcp_host: Use shared gcp credentials + REST helpers utils::gcp: Move/add gcp credentials management to shared file utils::rest::client: Add formatter for seastar::http::reply utils::rest::client: Add helper routines for simple REST calls utils::http: Make shared system trust certificates public
Scylla in-source tests.
For details on how to run the tests, see docs/dev/testing.md
Shared C++ utils, libraries are in lib/, for Python - pylib/
alternator - Python tests which connect to a single server and use the DynamoDB API unit, boost, raft - unit tests in C++ cqlpy - Python tests which connect to a single server and use CQL topology* - tests that set up clusters and add/remove nodes cql - approval tests that use CQL and pre-recorded output rest_api - tests for Scylla REST API Port 9000 scylla-gdb - tests for scylla-gdb.py helper script nodetool - tests for C++ implementation of nodetool
If you can use an existing folder, consider adding your test to it. New folders should be used for new large categories/subsystems, or when the test environment is significantly different from some existing suite, e.g. you plan to start scylladb with different configuration, and you intend to add many tests and would like them to reuse an existing Scylla cluster (clusters can be reused for tests within the same folder).
To add a new folder, create a new directory, and then
copy & edit its suite.ini.