3ca2e6ddda
Several updates and improvements to the retryable HTTP client functionality, as well as enhancements to error handling and integration with AWS services, as part of this PR. Below is a summary of the changes: - Moved the retryable HTTP client functionality out of the S3 client to improve modularity and reusability across other services like AWS STS. - Isolated the retryable_http_client into its own file, improving clarity and maintainability. - Added a make_request method that introduces a response-skipping handler. - Introduced a custom error handler constructor, providing greater flexibility in handling errors. - Updated the STS and Instance Metadata Service credentials providers to utilize the new retryable HTTP client, enhancing their robustness and reliability. - Extended the AWS error list to handle errors specific to the STS service, ensuring more granular and accurate error management for STS operations. - Enhanced error handling for system errors returned by Seastar’s HTTP client, ensuring smoother operations. - Properly closed the HTTP client in instance_profile_credentials_provider and sts_assume_role_credentials_provider to prevent resource leaks. - Reduced the log severity in the retry strategy to avoid SCT test failures that occur when any log message is tagged as an ERROR. No backport needed since we dont have any s3 related activity on the scylla side been released Closes scylladb/scylladb#21933 * github.com:scylladb/scylladb: s3_client: Adjust Log Severity in Retry Strategy aws_error: Enhance error handling for AWS HTTP client aws_error: Add STS specific error handling credentials_providers: Close retryable clients in Credentials Providers credentials_providers: Integrate retryable_http_client with Credentials Providers s3_client: enhance `retryable_http_client` functionality s3_client: isolate `retryable_http_client` s3_client: Prepare for `retryable_http_client` relocation s3_client: Remove `is_redirect_status` function s3_client: Move retryable functionality out of s3 client
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.