Andrew Gaul

Yeah I could add this functionality, similar to how the older filesystem provider works around lack of support. jimfs makes this easy to test (although I used [libnoattr](https://github.com/gaul/libnoxattr) last time...

CI fails with: ``` xattr: test-s3fs-31417.txt_rm_xattr.vijEdRbj: No such xattr: key ```

It appears that the S3 client added metadata with characters that Azure does not support. Consider remapping them via https://github.com/gaul/s3proxy/wiki/Middleware-user-metadata-replacer.

Can you check which characters your client is sending? You can do this by running S3Proxy with more logging: ``` java -DLOG_LEVEL=trace -jar /path/to/s3proxy ```

Azure Datalake uses a different API than Azure Blob: https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-directory-file-acl-java?tabs=azure-ad S3Proxy does not support this. Adding this would be straightforward if you use the azureblob-sdk as a template: https://github.com/gaul/s3proxy/tree/master/src/main/java/org/gaul/s3proxy/azureblob

apache/jclouds#208 will address this. For now you can override `jclouds.version` with 2.7.0-SNAPSHOT and build S3Proxy to include this fix.

You might also try the new azureblob-sdk provider tracked by #606 which works today in master.

Thank you for your contribution @cstamas! I successfully pushed a new snapshot and will try to run a new release now.

Modernizer has only simple bytecode-level checks with no flow control so it cannot understand if isPresent { get } sequences. But I would encourage you to call `orElseThrow` instead of...

Looks like I missed a step! I manually run these commands for every release: ```sh git rebase upstream/master mvn versions:set -DnewVersion=1.2.2 git add -p git commit -m 'modernizer-maven-plugin 1.2.2 release'...