JustinKyleJames

> one conflict now Resolved it and pushed.

> I just realized that the `is_host_in_host_list` function takes a `const std::string_view&`. We need to remove the ampersand from that parameter. > > Let's get this in as-is so that...

Added pound.

> @JustinKyleJames - Do you know if it's appropriate to call close on the L3 descriptors opened in the S3 resource plugin, if indeed there are any to close? I...

I executed the test Alan describes above against an S3 resource in both cache and cacheless mode. Everything worked fine.

We will have a host_list parameter in the resource context string. If this exists, only the hosts in the list will be considered available to serve the request. Also note...

Closing this as it has been merged.

I just double checked that this is still an issue with both 4.2.11 and 4.3.0. Reproducing the error: First, here is the S3 archive configuration showing the S3_STORAGE_CLASS and S3_RESTORATION_TIER....

Closing

This has been merged so closing it.