Enable shared Azure and OneLake test resources for maintainers #773

Activity

1. alamb commented on Jun 22, 2026

   

   alamb

   on Jun 22, 2026

   Contributor

   More actions

   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 🤔

   👍React with 👍1Reacted by Kevin Liu
2. kevinjqliu commented on Sep 29, 2026

   

   kevinjqliu

   on Sep 29, 2026

   ContributorAuthor

   More actions

   Following up on this, I took some time to investigate and I see 3 parallel paths.

   1. I have $150/month in Azure credit courtesy of being an MSFT FTE, and I'm happy to provide it as a way to improve the testing strategy against real Azure endpoints. It automatically stops once the credit is reached within a month, so there's no additional financial risk to me 😄

      I think this fits well with @alamb's suggestion above. Instead of putting this into the main CI, we can have a semi-automated way to run the integration tests against real Azure resources for specific PRs. I can also help provide OneLake access for testing.

   2. Microsoft also has a [Free and Open Source Software Fund (FOSS Fund)](https://github.com/microsoft/foss-fund) specifically for supporting open source projects. For example, apache/solr was recently accepted. Any MSFT FTE can nominate a project, and I've already nominated this one. Will report back if I hear anything.

   3. Since this is an Apache project, another path is to ask ASF if they can help provide Azure resources. ASF's [Targeted Sponsorship Policy](https://www.apache.org/foundation/docs/targeted-sponsorship-policy.html) specifically calls out Microsoft Azure Credits as an example. This seems like a better long-term home for shared test infrastructure than tying it to my personal Azure subscription.
3. alamb commented on Oct 5, 2026

   

   alamb

   on Oct 5, 2026 via email

   Contributor

   More actions

   Thank you for the research Kevin. I don't think I'll have the bandwidth to drive this in any meaningful way and I worrya bout additional infrastructure / testing that we don't have the bandwidth to maintain / fix when broken I wonder if we could move the testing into another repo (rather than in this one) -- Other tan conveneince I don't think there is any technical reason we can't run tests un another repo on PRs to this one

   …

   On Tue, Sep 29, 2026 at 4:22 PM Kevin Liu ***@***.***> wrote: *kevinjqliu* left a comment (apache/arrow-rs-object-store#773) <#773 (comment)> Following up on this, I took some time to investigate and I see 3 parallel paths. 1. I have $150/month in Azure credit courtesy of being an MSFT FTE, and I'm happy to provide it as a way to improve the testing strategy against real Azure endpoints. It automatically stops once the credit is reached within a month, so there's no additional financial risk to me 😄 I think this fits well with @alamb <https://github.com/alamb>'s suggestion above. Instead of putting this into the main CI, we can have a semi-automated way to run the integration tests against real Azure resources for specific PRs. I can also help provide OneLake access for testing. 2. Microsoft also has a [Free and Open Source Software Fund (FOSS Fund) <https://github.com/microsoft/foss-fund>]( https://github.com/microsoft/foss-fund) specifically for supporting open source projects. For example, apache/solr was recently accepted. Any MSFT FTE can nominate a project, and I've already nominated this one. Will report back if I hear anything. 3. Since this is an Apache project, another path is to ask ASF if they can help provide Azure resources. ASF's [Targeted Sponsorship Policy <https://www.apache.org/foundation/docs/targeted-sponsorship-policy.html> ]( https://www.apache.org/foundation/docs/targeted-sponsorship-policy.html) specifically calls out Microsoft Azure Credits as an example. This seems like a better long-term home for shared test infrastructure than tying it to my personal Azure subscription. — Reply to this email directly, view it on GitHub <#773?email_source=notifications&email_token=AADXZMLYMAWU6BLJNEIFMZD5RQKZJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKOBZHAYDOOBWGU4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5898078658>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADXZMJHE22QUU4XLTY5FAL5RQKZJAVCNFSNUABFKJSXA33TNF2G64TZHM4TKMRQHE3TANBWHNEXG43VMU5TINZQG4ZTMMBSG4Z2C5QC> . You are receiving this because you were mentioned.Message ID: ***@***.***>
4. crepererum commented on Oct 6, 2026

   

   crepererum

   on Oct 6, 2026

   Contributor

   More actions

   TBH if tests aren't "convenient" and/or don't run on most/all PRs, then I think they have rather limited value. Even today people can test manually against an actual cloud provider. The issue is rather that a) most people don't and b) the emulators that we have don't reflect the actual upstream behavior.

   👍React with 👍1Reacted by Andrew Lamb
5. alamb commented on Oct 6, 2026

   

   alamb

   on Oct 6, 2026

   Contributor

   More actions

   TBH if tests aren't "convenient" and/or don't run on most/all PRs,

   Yeah, this is why I was thinking something automated (but in another repository) could at least give us coverage without manually intervention (unless there is a failure)