alamb commented on issue #773: URL: https://github.com/apache/arrow-rs-object-store/issues/773#issuecomment-4768610027
What I think is missing from our Azure/OneLake testing strategy is 1. Being able to test a proposed change against a real endpoint to make sure the 1) feature does what is desired, and 2) doesn't break anything else. 2. Ensure that as the backend service continues to evolve, the object_store APIs keep working as designed We currently use the "Azurite" emulator for this in the integration tests, but that comes with the same caveats as any emulator. I am not sure that trying to integrate a real azure bucket into the automated CI is a good idea due to the maintenance burden of keeping it working, secret management, etc. Maybe we could make a semi-automated way to run the tests with some given credentials and then trigger that outside the main repo for particular PRs 🤔 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
