discourse/spec/lib/backup_restore
Martin Brennan 0568d36133
FIX: Use dualstack S3 endpoint for direct uploads (#29611)
When we added direct S3 uploads to Discourse, which use
presigned URLs, we never took into account the dualstack
endpoints for IPv6 on S3.

This commit fixes the issue by using the dualstack endpoints
for presigned URLs and requests, which are used in the
get-presigned-put and batch-presign-urls endpoints used when
directly uploading to S3.

It also makes regular S3 requests for `put` and so on use
dualstack URLs. It doesn't seem like there is a downside to
doing this, but a bunch of specs needed to be updated to reflect this.
2024-11-07 11:06:39 +10:00
..
backup_file_handler_multisite_spec.rb
backup_file_handler_spec.rb
backuper_spec.rb
database_restorer_multisite_spec.rb
database_restorer_spec.rb FIX: Restoring backup could fail due to missing discourse_functions (#29332) 2024-10-22 16:13:01 +02:00
local_backup_store_spec.rb
meta_data_handler_spec.rb
s3_backup_store_spec.rb FIX: Use dualstack S3 endpoint for direct uploads (#29611) 2024-11-07 11:06:39 +10:00
shared_context_for_backup_restore.rb
shared_examples_for_backup_store.rb FIX: Use dualstack S3 endpoint for direct uploads (#29611) 2024-11-07 11:06:39 +10:00
system_interface_multisite_spec.rb
system_interface_spec.rb
uploads_restorer_spec.rb