This PR adds support for validating the .NET driver in Azure Functions to ensure that a release build doesn't break one of the most popular 3rd-party platform that .NET customers would likely use for serverless functions.
The pipeline references a private repo, fauna/testtools, which just contains a simple Hello World app and the script collateral needed to publish the Azure Function app.
Motivation and context
BT-4442
How was the change tested?
Tested the setup scripts, test case, and Dockerfile build locally against real Azure; the image build part of the pipeline may require some iteration.
Screenshots (if appropriate):
Change types
[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (backwards-incompatible fix or feature)
Checklist:
[ ] My code follows the code style of this project.
[ ] My change requires a change to Fauna documentation.
[ ] My change requires a change to the README, and I have updated it accordingly.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Description
This PR adds support for validating the .NET driver in Azure Functions to ensure that a release build doesn't break one of the most popular 3rd-party platform that .NET customers would likely use for serverless functions.
The pipeline references a private repo,
fauna/testtools
, which just contains a simple Hello World app and the script collateral needed to publish the Azure Function app.Motivation and context
BT-4442
How was the change tested?
Tested the setup scripts, test case, and Dockerfile build locally against real Azure; the image build part of the pipeline may require some iteration.
Screenshots (if appropriate):
Change types
Checklist:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.