Add azdo provider by vhvb1989 · Pull Request #743 · Azure/azure-dev

vhvb1989 · 2022-09-23T21:59:55Z

fix #737
fix #750
This PR fixes #101, #708, #699 and #702 and adds support for Azure DevOps an SCM and CI provider.

This new workflow enables the following:

Pipeline named providers for GitHub github and Azure DevOps azdo
The provider can be specified in two ways:
- via azure.yaml by defining the following section:
```
pipelines:
   - provider: azdo
```
  This providers a permanent mechanism for switcing to Azure DevOps as a pipeline provider.
- Via the --provider flag
```
 azd pipeline config --provider azdo
```
  This method updates the provider for only this command invocation. Subsequent pipeline config commands will default to github, unless --provider is passed in.
Detection of provider based on .azdo or .github in the template augments the above behavior.
- If only a .github folder exists, it is assumed the provider is github if azdo is set as a provider value, this will result in an error
- If only a .azdo folder exists, it is assume the provider is azdo. If github is set as the provider value, this will result in an error.
- If both .azdo and .github folder exists, github is selected by default if --provider argument is not set and/or if there's not an pipeline: provider entry in azure.yaml
- When pipeline:provider is set in azure.yaml and --provider argument is also used for running azd pipeline config. The --provider argument overrides the settings from azure.yaml
AzDo provider supports using an existing project.
AzDo provider supports creating a new project.
AzDo provider supports using an existing repo.
AzDo provider supports creating a new repo in a project.
PAT authentication is used to push to the new repo, and the tool checks for credential helper and offers to set it to store to make subsequent pushes easier.
If a PAT is not provided, the tool will ask the user for a PAT and ask the user if they would like to store it.
If an organization name is not provided via an Environment Variable, the user will be prompted for an organization name and it will be stored in the environment file.
AzDo provider creates a build policy to ensure pushes to default branch are disabled and require a successful pipeline invocation.
Deployment Pipeline is created
Service Connection is created to allow the pipeline to deploy to azure.
Initial pipeline deployment is queued to follow the github behavior.

This was tested with a full deployment of todo-python-mongo using an Azure DevOps Pipeline.

Co-authored-by: Hadwa Gaber <hadwaa@microsoft.com>

…o add-azdo-provider

… and test based on linting results.

* Refactor to introduce new azdo package * refactor azdo code to multiple files in azdo package * Added azdo connection test and refactored provider * Added azdo provider initial tests * added more azdo provider tests * Adding test to verify save env config in azdo provider * Updating displayed urls to aka.ms

…to azdo-pr-updates

…o azdo-pr-updates

Co-authored-by: Wei Lim <weikanglim@gmail.com>

wbreza

Looks good overall. Added a few more comments but nothing blocking at this point.

ellismg

Thanks for all the hard work here, @vhvb1989.

One stylistic comment, there's a bunch of places where we set a bunch of locals, then construct an args parameter (which we also set to a local) and then make a call passing in the args object. It might be easier to read if we instead just creatied the options object at the call site. I think that combined with adding some helper which basically looks like refOf[T any](value T) *T would let us collapse the number of locals we have and move values closer to where they end up being used.

I personally like this style because when reading code if we assign something to a local my mind starts to track it, whereas when we just create a value inside the argument list of a function, we are calling I sort of know "okay, this stuff is just specific to this call" and my mind spends less time lingering on it.

azure-sdk · 2022-09-27T07:00:14Z

Repoman Generation Results

Repoman pushed changes to remotes for the following projects: