6 Commits

Author SHA1 Message Date
nharper285
2391d927f7
Updating yml file to run config endpoint command with tenant/authority ID. (#339)
## 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.
2020-11-30 14:54:42 +00:00
Anshuman Goel
30ba30d609
Add --upgrade to the Azure Devops deployment pipeline (#304) 2020-11-12 11:34:31 -05:00
Anshuman Goel
382003e4d0
Comment update to register app as owner (#262) 2020-11-11 17:58:30 -05:00
Anshuman Goel
0e04309e33
Adding linting for contrib/deploy-onefuzz-via-azure-devops (#256) 2020-11-03 11:39:33 -05:00
anslutsk
d2996656f6
Updated deploy-onefuzz-via-azure-devops (#233) 2020-10-29 18:22:36 -04:00
Anshuman Goel
640091f8bc
ADO Pipeline to update a onefuzz instance with the latest release (#208) 2020-10-28 15:31:42 -04:00