Skip to content

[Utilities] Updated DevOps Registration #1611

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AlexanderSehr merged 1 commit into from
Jul 4, 2022
Merged

[Utilities] Updated DevOps Registration #1611

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 3 additions & 19 deletions utilities/tools/AzureDevOps/Register-AzureDevOpsPipeline.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,9 +30,6 @@ Defaults to 'Azure/ResourceModules'
Optional. The type of source repository. Either 'GitHub' or 'tfsgit' (for Azure DevOps).
Defaults to 'GitHub'.

.PARAMETER GitHubPAT
Optional. A personal access token for the GitHub repository with the source code.

.PARAMETER GitHubServiceConnectionName
Optional. The pre-created service connection to the GitHub source repository if the pipeline files are in GitHub.
It is recommended to create the service connection using oAuth.
Expand All @@ -42,7 +39,9 @@ Required. The access token with appropriate permissions to create Azure Pipeline
Usually the System.AccessToken from an Azure Pipeline instance run has sufficient permissions as well.
Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/access-tokens?view=azure-devops&tabs=yaml#how-do-i-determine-the-job-authorization-scope-of-my-yaml-pipeline
Needs at least the permissions:
- Release: Read, write, execute & manage
- Agent Pool: Read
- Build: Read & execute
- Service Connections: Read & query

.PARAMETER BranchName
Optional. Branch name for which the pipelines will be configured.
Expand All @@ -59,18 +58,6 @@ Defaults to '.azuredevops/modulePipelines'.
.PARAMETER CreateBuildValidation
Optional. Create an additional pull request build validation rule for the pipelines.

.EXAMPLE
$inputObject = @{
OrganizationName = 'Contoso'
ProjectName = 'CICD'
SourceRepository = 'Azure/ResourceModules'
GitHubPAT = '<Placeholder>'
AzureDevOpsPAT = '<Placeholder>'
}
Register-AzureDevOpsPipeline @inputObject

Registers all pipelines in the default path in the DevOps project [Contoso/CICD] by leveraging the given AzureDevOpsPAT and creating a service connection to GitHub using the provided GitHubPAT

.EXAMPLE
$inputObject = @{
OrganizationName = 'Contoso'
Expand Down Expand Up @@ -126,9 +113,6 @@ function Register-AzureDevOpsPipeline {
[ValidateSet('gitHub', 'tfsgit')]
[string] $SourceRepositoryType = 'gitHub',

[Parameter(Mandatory = $false)]
[string] $GitHubPAT,

[Parameter(Mandatory = $false)]
[string] $GitHubServiceConnectionName = $SourceRepository,

Expand Down