mirror of
https://github.com/microsoft/onefuzz.git
synced 2025-06-07 15:51:33 +00:00
2391d927f7
## Summary of the Pull Request Originally, the yml file printed out a semi-generalized _onefuzz config --endpoint_ comman. This command did have a specified _--authority_ and so it used the Microsoft id by default. To enable users to work with OneFuzz on tenants other than the standard Microsoft tenant, we have added a _--authority_ parameter that is printed out at the end of the deployment. ## PR Checklist * [ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx ## Info on Pull Request Changes to the yml file. ## Validation Steps Performed We have made this change to our local automation repository and tested an automated deployment pipeline with this change.
What is this for?
This section of code contains scripts which help to deploy latest releases of OneFuzz at demand. It uses Azure DevOps Build Pipeline.
The script deploy-onefuzz.yml can be used saved in Azure DevOps Build Pipeline or can be stored in the repository and can be pointed to it.
It also contain supporting python scripts which helps to fetch latest version and artifacts from OneFuzz GitHub repository.
How to use it?
This script is intended only for deploying newer updates. There are certain set of pipeline variables needs to be set as mentioned in deploy-onefuzz.yml for authentication purposes to the OneFuzz instance.