ExternalVendorCode/onefuzz
1
0
Fork 0
mirror of https://github.com/microsoft/onefuzz.git synced 2025-06-19 13:03:44 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
4c2679d61e28c5958d5e708869c40a72e73957e1
onefuzz/src/api-service
History
bmc-msft 4c2679d61e Re-add windows ssh key (#390) 
Adds a scaleset specific setup script, which allows us to save the scaleset based SSH keys into the VM on setup.
2021-01-04 19:52:27 +00:00
..
__app__
Re-add windows ssh key (#390)
2021-01-04 19:52:27 +00:00
tests
Event based webhooks (#296)
2020-11-12 17:44:42 -05: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
Declarative templates (#266)
2020-11-17 16:00:09 -05: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
re-add black to lint stages (#45)
2020-09-29 16:35:41 -04: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>