Microsoft.Web sites/sourcecontrols

  • 3 minutes to read

The sites/sourcecontrols resource type can be deployed to: Resource groups.

To learn about resource group deployments, see Bicep or ARM template.

Template format

To create a Microsoft.Web/sites/sourcecontrols resource, add the following Bicep or JSON to your template.

resource symbolicname 'Microsoft.Web/sites/sourcecontrols@2021-02-01' = {
  name: 'web'
  kind: 'string'
  parent: parentSymbolicName
  properties: {
    branch: 'string'
    deploymentRollbackEnabled: bool
    gitHubActionConfiguration: {
      codeConfiguration: {
        runtimeStack: 'string'
        runtimeVersion: 'string'
      }
      containerConfiguration: {
        imageName: 'string'
        password: 'string'
        serverUrl: 'string'
        username: 'string'
      }
      generateWorkflowFile: bool
      isLinux: bool
    }
    isGitHubAction: bool
    isManualIntegration: bool
    isMercurial: bool
    repoUrl: 'string'
  }
}

Property values

sites/sourcecontrols

Name Description Value
type The resource type

For Bicep, set this value in the resource declaration.		 'Microsoft.Web/sites/sourcecontrols'
apiVersion The resource api version

For Bicep, set this value in the resource declaration.		 '2021-02-01'
name The resource name

See how to set names and types for child resources in Bicep or JSON ARM templates.		 'web'
kind Kind of resource. string
parent In Bicep, you can specify the parent resource for a child resource. You only need to add this property when the child resource is declared outside of the parent resource.

For more information, see Child resource outside parent resource.		 parentSymbolicName
properties SiteSourceControl resource specific properties SiteSourceControlProperties

SiteSourceControlProperties

Name Description Value
branch Name of branch to use for deployment. string
deploymentRollbackEnabled {code}true{/code} to enable deployment rollback; otherwise, {code}false{/code}. bool
gitHubActionConfiguration The GitHub action configuration. GitHubActionConfiguration
isGitHubAction {code}true{/code} if this is deployed via GitHub action. bool
isManualIntegration {code}true{/code} to limit to manual integration; {code}false{/code} to enable continuous integration (which configures webhooks into online repos like GitHub). bool
isMercurial {code}true{/code} for a Mercurial repository; {code}false{/code} for a Git repository. bool
repoUrl Repository or source control URL. string

GitHubActionConfiguration

Name Description Value
codeConfiguration The GitHub action code configuration. GitHubActionCodeConfiguration
containerConfiguration The GitHub action container configuration. GitHubActionContainerConfiguration
generateWorkflowFile Workflow option to determine whether the workflow file should be generated and written to the repository. bool
isLinux This will help determine the workflow configuration to select. bool

GitHubActionCodeConfiguration

Name Description Value
runtimeStack Runtime stack is used to determine the workflow file content for code base apps. string
runtimeVersion Runtime version is used to determine what build version to set in the workflow file. string

GitHubActionContainerConfiguration

Name Description Value
imageName The image name for the build. string
password The password used to upload the image to the container registry. string
serverUrl The server URL for the container registry where the build will be hosted. string
username The username used to upload the image to the container registry. string

Quickstart templates

The following quickstart templates deploy this resource type.

Template Description
PubNub Realtime Gateway for Azure Event Hubs

Deploy to Azure		 The PubNub Realtime Gateway for Azure provides a realtime data stream bridge between the PubNub Data Stream Network and Azure Event Hubs. -- consider it a bi-directional bridge between PubNub and Azure!
WordPress on App Service with MySQL In App

Deploy to Azure		 This template deploys a WordPress Web App on a Windows App Service with MySQL in app
eShop Website with ILB ASE

Deploy to Azure		 An App Service Environment is a Premium service plan option of Azure App Service that provides a fully isolated and dedicated environment for securely running Azure App Service apps at high scale, including Web Apps, Mobile Apps, and API Apps.
Create a zero touch Azure Cosmos account and Azure Web App

Deploy to Azure		 This template creates an Azure Cosmos account, injects the Cosmos DB endpoint and keys into Azure Web App settings, then deploys an ASP MVC web app from GitHub.
Azure Logic App with Function

Deploy to Azure		 This template creates a Serverless app in Azure with Logic Apps and Functions. The Logic App triggers on an HTTP POST, calls the Azure Function, and returns the response.
App Service Quickstart - Windows app

Deploy to Azure		 This template is to be used with /azure/app-service/quickstart-arm-template
Provision a function app with source deployed from GitHub

Deploy to Azure		 This template deploys a Function App hosted in a new dedicated App Service Plan. The Function App has a child resource that enables continous integration and deploys the function code from a GitHub repository.
WebApp GitHub

Deploy to Azure		 This template allows you to create an WebApp linked with a GitHub Repository linked.
App Service Quickstart - Windows app

Deploy to Azure		 This template is to be used with /azure/app-service/quickstart-arm-template