Skip to content

CLHdevOps/AzureDevBoxDevEnvironments

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

21 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Dev Box and Dev Environments

image

Deployment examples

Use the follow commands (using Az PowerShell)

Providing a PAT, which will create the keyvault to store it

$ghPATToken = ConvertTo-SecureString -String "PAT_TOKEN" -AsPlainText -Force
New-AzDeployment -Name DevBox -Location EastUS2 -TemplateFile .\src\main.bicep -TemplateParameterFile .\src\main.parameters.jsonc -keyVaultPatSecretValue $ghPATToken -Verbose

Deploy using pipeline

  1. Open the Bicep parameters file, located under \src\main.parameters.jsonc

  2. Configure the following parameters

    Variable Type Required Description
    environmentName Text Yes Name of the environment which is used to generate a short unique hash used in all resources
    Location Text Yes Primary location for all resources, determine availbility in desired region
    resourceGroupName Text Yes The resource group name where the resources will be deployed
    deployVnet Boolean Yes True for initial deployment of the virtual network. If it's already created, this should be false
    devboxRbac GUID/Text Yes Provide the principalId and roleType (User or Group)
  3. Open the YAML pipeline located under .pipelines\devbox-deply.yml and modify the parameters.

  4. As indicated, ensure the Service connection has 'Microsoft.Authorization/roleAssignments/write' permissions.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Bicep 100.0%