ExternalVendorCode/onefuzz
1
0
Fork 0
mirror of https://github.com/microsoft/onefuzz.git synced 2025-06-18 12:48:07 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
2c72bd590fbdf73b75eebdf4a3282760b38e4732
onefuzz/src/api-service
History
Joe Ranweiler 2c72bd590f Add generic coverage task (#763) 
**Todo:**
- [x] Finalize format for coverage file(s)
- [x] Add service support
- [x] Integration test
- [x] Merge #926 
- [x] Merge #929
2021-06-03 23:36:00 +00:00
..
__app__
Add generic coverage task (#763)
2021-06-03 23:36:00 +00:00
tests
work around issue with discriminated typed unions (#939)
2021-06-02 16:40:58 +00:00
.flake8
initial public release
2020-09-18 12:21:04 -04:00
.gitignore
initial public release
2020-09-18 12:21:04 -04:00
dev-deploy.ps1
Adding version as a param to dev-deploy script (#239)
2020-11-02 14:05:13 -05:00
dev-deploy.sh
Declarative templates (#266)
2020-11-17 16:00:09 -05:00
mypy.ini
Add StopIfFree node command to tell free nodes to stop asking for new work (#866)
2021-05-07 13:55:50 -04:00
pytest.ini
initial public release
2020-09-18 12:21:04 -04:00
README.md
initial public release
2020-09-18 12:21:04 -04:00
requirements-dev.txt
add security auditing of python code using Bandit during CICD (#491)
2021-02-01 16:51:03 -05:00

README.md

If you are doing development on the API service, you can build and deploy directly to your own instance using the azure-functions-core-tools.

From the api-service directory, do the following:

func azure functionapp publish <instance>

While Azure Functions will restart your instance with the new code, it may take a while. It may be helpful to restart your instance after pushing by doing the following:

az functionapp restart -g <group> -n <instance>