@microsoft/teamsfx-core 2.0.1 → 2.0.2-alpha.bd1241522.0

package/templates/plugins/resource/cicd/jenkins/Jenkinsfile.cd

@@ -1,77 +0,0 @@
-{{=<% %>=}}
-// This is just an example workflow for continuous deployment.
-// The example workflow is expected to run on Ubuntu stable versions, for example, 20.04lts and later.
-// You should customize it to meet your own requirements.
-pipeline {
-    // To customize the agent field, please refer to https://www.jenkins.io/doc/book/pipeline/syntax/#agent.
-    agent any
-
-    // To customize triggers, please refer to https://www.jenkins.io/doc/book/pipeline/syntax/#triggers.
-    triggers { pollSCM('H */4 * * 1-5') }
-
-    // To learn more about environment, please refer to https://www.jenkins.io/doc/book/pipeline/syntax/#environment.
-    environment {
-<%#hosting_type_contains_spfx%>
-        M365_ACCOUNT_NAME = credentials('M365_ACCOUNT_NAME')
-        M365_ACCOUNT_PASSWORD = credentials('M365_ACCOUNT_PASSWORD')
-        M365_TENANT_ID = credentials('M365_TENANT_ID')
-<%/hosting_type_contains_spfx%>
-        // To enable M365 account login by environment variables and non-interactive mode. 
-        CI_ENABLED = 'true'
-        // To specify the env name for multi-env feature.
-        TEAMSFX_ENV_NAME = '<%env_name%>'
-        // To specify the version of TTK CLI for use.
-        TEAMSFX_CLI_VERSION = '1.*'
-    }
-
-    stages {
-        // Setup environment.
-        stage('Setup environment') {
-            steps {
-                // Install the TTK CLI for later use.
-                sh 'npm install @microsoft/teamsfx-cli@${TEAMSFX_CLI_VERSION}'
-                // Check the version of teamsfx.
-                sh 'npx teamsfx -v'
-            }
-        }
-
-        // Build the project.
-        // The way to build the current project depends on how you scaffold it.
-        // Different folder structures require different commands set.
-        // 'npm ci' may be used here to install dependencies and it depends on package-lock.json.
-        // If you prefer to use 'npm ci', please make sure to commit package-lock.json first, or just change it to 'npm install'.
-        stage('Build the project') {
-            steps {
-                sh '<%build_script%>'
-            }
-        }
-
-        // Run unit test.
-        // Currently, no opinionated solution for unit test provided during scaffolding, so,
-        // set up any unit test framework you prefer (for example, mocha or jest) and update the commands accordingly in below.
-        // stage('Run unit test') {
-        //     steps {
-        //         sh 'npm run test'
-        //     }
-        // }
-<%#hosting_type_contains_azure%>
-
-        stage('Login Azure by service principal') {
-            environment {
-              SP_NAME = credentials('AZURE_SERVICE_PRINCIPAL_NAME') 
-              SP_PASSWORD = credentials('AZURE_SERVICE_PRINCIPAL_PASSWORD') 
-              TENANT_ID = credentials('AZURE_TENANT_ID') 
-            }
-            steps {
-                sh 'npx teamsfx account login azure --service-principal --username ${SP_NAME} --password ${SP_PASSWORD} --tenant ${TENANT_ID}'
-            } 
-        }
-<%/hosting_type_contains_azure%>
-
-        stage('Deploy to hosting environment') {
-            steps {
-                sh 'npx teamsfx deploy --env ${TEAMSFX_ENV_NAME}<%#cloud_resources_contains_apim%> --api-version v1 --open-api-document openapi/openapi.json --api-prefix <%api_prefix%><%/cloud_resources_contains_apim%>'
-            }
-        }
-    }
-}

package/templates/plugins/resource/cicd/jenkins/Jenkinsfile.ci

@@ -1,34 +0,0 @@
-{{=<% %>=}}
-// This is just an example workflow for continuous integration.
-// The example workflow is expected to run on Ubuntu stable versions, for example, 20.04lts and later.
-// You should customize it to meet your own requirements.
-// The file may be renamed to Jenkinsfile, and put into dev branch.
-pipeline {
-    // To customize the agent field, please refer to https://www.jenkins.io/doc/book/pipeline/syntax/#agent.
-    agent any
-
-    // To customize triggers, please refer to https://www.jenkins.io/doc/book/pipeline/syntax/#triggers.
-    triggers { pollSCM('H */4 * * 1-5') }
-
-    stages {
-        // Build the project.
-        // The way to build the current project depends on how you scaffold it.
-        // Different folder structures require different commands set.
-        // 'npm ci' may be used here to install dependencies and it depends on package-lock.json.
-        // If you prefer to use 'npm ci', please make sure to commit package-lock.json first, or just change it to 'npm install'.
-        stage('Build the project') {
-            steps {
-                sh '<%build_script%>'
-            }
-        }
-
-        // Run unit test.
-        // Currently, no opinionated solution for unit test provided during scaffolding, so,
-        // set up any unit test framework you prefer (for example, mocha or jest) and update the commands accordingly in below.
-        // stage('Run Unit Test') {
-        //    steps {
-        //        sh 'npm run test'
-        //    }
-        // }
-    }
-}

package/templates/plugins/resource/cicd/jenkins/Jenkinsfile.provision

@@ -1,79 +0,0 @@
-{{=<% %>=}}
-// This is just an example workflow for provision.
-// The example workflow is expected to run on Ubuntu stable versions, for example, 20.04lts and later.
-// You should customize it to meet your own requirements.
-pipeline {
-    // To customize the agent field, please refer to https://www.jenkins.io/doc/book/pipeline/syntax/#agent.
-    agent any
-
-    // Manually trigger this workflow.
-    // To customize triggers, please refer to https://www.jenkins.io/doc/book/pipeline/syntax/#triggers.
-    // triggers { pollSCM('H */4 * * 1-5') }
-
-    // To learn more about environment, please refer to https://www.jenkins.io/doc/book/pipeline/syntax/#environment.
-    environment {
-        M365_ACCOUNT_NAME = credentials('M365_ACCOUNT_NAME')
-        M365_ACCOUNT_PASSWORD = credentials('M365_ACCOUNT_PASSWORD')
-        M365_TENANT_ID = credentials('M365_TENANT_ID')
-        // To enable M365 account login by non-interactive mode. 
-        CI_ENABLED = 'true'
-
-        // To specify the env name for multi-env feature.
-        TEAMSFX_ENV_NAME = '<%env_name%>'
-        // To specify the version of TTK CLI for use.
-        TEAMSFX_CLI_VERSION = '1.*'
-    }
-
-    stages {
-        // Setup environment.
-        stage('Setup environment') {
-            steps {
-                // Install the TTK CLI for later use.
-                sh 'npm install @microsoft/teamsfx-cli@${TEAMSFX_CLI_VERSION}'
-                // Check the version of teamsfx.
-                sh 'npx teamsfx -v'
-            }
-        }
-<%#hosting_type_contains_azure%>
-
-        stage('Login Azure by service principal') {
-            environment {
-              SP_NAME = credentials('AZURE_SERVICE_PRINCIPAL_NAME') 
-              SP_PASSWORD = credentials('AZURE_SERVICE_PRINCIPAL_PASSWORD') 
-              TENANT_ID = credentials('AZURE_TENANT_ID') 
-            }
-            steps {
-                sh 'npx teamsfx account login azure --service-principal --username ${SP_NAME} --password ${SP_PASSWORD} --tenant ${TENANT_ID}'
-            } 
-        }
-<%/hosting_type_contains_azure%>
-
-        // We suggest to do the `npx teamsfx provision` step manually or in a separate pipeline. The following steps are for your reference.
-        // After provisioning, you should commit necessary files under .fx into the repository.
-        stage('Provision hosting environment') {
-<%#hosting_type_contains_azure%>            
-            environment {
-                AZURE_SUBSCRIPTION_ID = credentials('AZURE_SUBSCRIPTION_ID')
-<%#cloud_resources_contains_sql%>
-                SQL_ADMIN_NAME = credentials('SQL_ADMIN_NAME')
-                SQL_PASSWORD = credentials('SQL_PASSWORD')
-<%/cloud_resources_contains_sql%>
-            }
-<%/hosting_type_contains_azure%>
-            steps {
-                sh 'npx teamsfx provision<%#hosting_type_contains_azure%> --subscription ${AZURE_SUBSCRIPTION_ID}<%/hosting_type_contains_azure%> --env ${TEAMSFX_ENV_NAME}<%#cloud_resources_contains_sql%> --sql-admin-name ${SQL_ADMIN_NAME} --sql-password ${SQL_PASSWORD}<%/cloud_resources_contains_sql%>'
-            }
-        }
-
-        stage('Commit provision configs if necessary') {
-            steps {
-                sh 'git config user.name "azdo-agent"'
-                sh 'git config user.email "azdo-agent@azure.com"'
-                sh 'git add .'
-                sh 'git commit -m "chore: commit provision configs"'
-                // Using awk to extract origin and branch name.
-                sh 'git push `echo $GIT_BRANCH | awk -F\'/\' \'{print $1, "HEAD:"$2}\'`'
-            }
-        }
-    }
-}

package/templates/plugins/resource/cicd/jenkins/Jenkinsfile.publish

@@ -1,57 +0,0 @@
-{{=<% %>=}}
-// This is just an example workflow for publish.
-// The example workflow is expected to run on Ubuntu stable versions, for example, 20.04lts and later.
-// You should customize it to meet your own requirements.
-pipeline {
-    // To customize the agent field, please refer to https://www.jenkins.io/doc/book/pipeline/syntax/#agent.
-    agent any
-
-    // Manually trigger this workflow.
-    // To customize triggers, please refer to https://www.jenkins.io/doc/book/pipeline/syntax/#triggers.
-    // triggers { pollSCM('H */4 * * 1-5') }
-
-    // To learn more about environment, please refer to https://www.jenkins.io/doc/book/pipeline/syntax/#environment.
-    environment {
-        M365_ACCOUNT_NAME = credentials('M365_ACCOUNT_NAME')
-        M365_ACCOUNT_PASSWORD = credentials('M365_ACCOUNT_PASSWORD')
-        M365_TENANT_ID = credentials('M365_TENANT_ID')
-        // To enable M365 account login by non-interactive mode. 
-        CI_ENABLED = 'true'
-        // To specify the env name for multi-env feature.
-        TEAMSFX_ENV_NAME = '<%env_name%>'
-        // To specify the version of TTK CLI for use.
-        TEAMSFX_CLI_VERSION = '1.*'
-    }
-
-    stages {
-        // Setup environment.
-        stage('Setup environment') {
-            steps {
-                // Install the TTK CLI for later use.
-                sh 'npm install @microsoft/teamsfx-cli@${TEAMSFX_CLI_VERSION}'
-                // Check the version of teamsfx.
-                sh 'npx teamsfx -v'
-            }
-        }
-
-        // This step is to pack the Teams App as zip file,
-        // which can be used to be uploaded onto Teams Client for installation.
-        stage('Package Teams App for publishing') {
-            steps {
-                sh 'npx teamsfx package --env ${TEAMSFX_ENV_NAME}'
-            }
-        }
-
-        stage('Upload Teams App package as artifact') {
-            steps {
-                archiveArtifacts artifacts: 'build/appPackage/appPackage.<%env_name%>.zip'
-            }
-        }
-
-        stage('Publish Teams App') {
-            steps {
-                sh 'npx teamsfx publish --env ${TEAMSFX_ENV_NAME}'
-            }
-        }
-    }
-}

package/templates/plugins/resource/cicd/jenkins/README.md

@@ -1,45 +0,0 @@
-# How to use pre-cooked pipelines on Jenkins
-
-## Prerequisites
-- Teams app projects are version controlled.
-- (Optional) An Microsoft 365 account. If you do not have Microsoft 365 account, apply one from [Microsoft 365 developer program](https://developer.microsoft.com/en-us/microsoft-365/dev-program). The Microsoft 365 account credentials are required for steps of provision, publish and deployment for SPFx projects. Any extra interactive verification steps should be disabled for the Microsoft 365 account, and please check details in sections below.
-- (Optional) An Azure service principal with necessary permissions. The Azure service principal credentials are required for steps of provision and deploy for Azure based projects.
-
-## Steps
-After the pre-cooked pipelines are scaffolded successfully, the following steps are expected to be performed:
-1. Commit and push your project source code to your remote repository, including the CI/CD Jenkinsfiles.
-1. Create corresponding Jenkins pipelines by following [Create your first Jenkins Pipeline](https://www.jenkins.io/doc/pipeline/tour/hello-world/).
-1. Configure necessary Jenkins credentials if your projects require credentials by checking into the Jenkinsfiles.
-1. Trigger your pipeline automatically, manually or do customization (Check the `triggers` section in Jenkinsfiles to find the triggers). More about triggers in Jenkins, refer to [Jenkins triggers](https://www.jenkins.io/doc/book/pipeline/syntax/#triggers).
-
-
-## Jenkins Credentials 
-Please follow [using-credentials](https://www.jenkins.io/doc/book/using/using-credentials/) to create credentials on Jenkins.
-
-|Name|Description|
-|---|---|
-|AZURE_SERVICE_PRINCIPAL_NAME|The service principal name of Azure used to provision resources.|
-|AZURE_SERVICE_PRINCIPAL_PASSWORD|The password of Azure service principal.|
-|AZURE_SUBSCRIPTION_ID|To identify the subscription in which the resources will be provisioned.|
-|AZURE_TENANT_ID|To identify the tenant in which the subscription resides.|
-|M365_ACCOUNT_NAME|The Microsoft 365 account for creating and publishing the Teams App.|
-|M365_ACCOUNT_PASSWORD|The password of the Microsoft 365 account.|
-|M365_TENANT_ID|To identify the tenant in which the Teams App will be created/published. This value is optional unless you have a multi-tenant account and you want to use another tenant. Read more on [how to find your Microsoft 365 tenant ID](https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-how-to-find-tenant).|
-> Note: Currently, a non-interactive authentication style for Microsoft 365 is used in CI/CD workflows, so please ensure that your Microsoft 365 account has sufficient privileges in your tenant and doesn't have multi-factor authentication or other advanced security features enabled. Please refer to the [Configure Microsoft 365 Credentials](https://github.com/OfficeDev/teamsfx-cli-action/blob/main/README.md#configure-m365azure-credentials-as-github-secret) to make sure you have disabled Multi-factor Authentication and Security Defaults for the credentials used in the workflow.
-
-> Note: Currently, service principal for Azure is used in CI/CD workflows, and to create Azure service principals for use, refer to [here](#how-to-create-azure-service-principals-for-use).
-
-# How to create Azure service principals for use?
-To provision and deploy resources targeting Azure inside CI/CD, you must create an Azure service principal for use.
-
-Briefly, the steps include:
-1. Register an Azure AD application in single tenant, and it requires sufficient permissions in your Azure AD tenant.
-2. Assign a role to your Azure AD application to access your Azure subscription, and `Contributor` role is recommended. 
-3. Create a new Azure AD application secret.
-4. Grab your tenant id, application id(AZURE_SERVICE_PRINCIPAL_NAME), and the secret(AZURE_SERVICE_PRINCIPAL_PASSWORD) for use.
-
-For detailed guidelines, refer to [the official document](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal). There're three ways to create service principal, [Azure portal](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal), [PowerShell](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-authenticate-service-principal-powershell), [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/create-an-azure-service-principal-azure-cli), and you can choose the way you like.
-
-# Additional Notes
-* [Create your first Jenkins Pipeline](https://www.jenkins.io/doc/pipeline/tour/hello-world/)
-* [Manage your apps with the Developer Portal for Microsoft Teams](https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/teams-developer-portal)

package/templates/plugins/resource/cicd_v2/azdo/README.md

@@ -1,48 +0,0 @@
-# How to use pre-cooked pipelines on Azure DevOps
-
-## Prerequisites
-- Teams app projects are version controlled by Azure DevOps.
-- (Optional) An Microsoft 365 account. If you do not have Microsoft 365 account, apply one from [Microsoft 365 developer program](https://developer.microsoft.com/en-us/microsoft-365/dev-program). The Microsoft 365 account credentials are required for steps of provision, publish and deployment for SPFx projects. Any extra interactive verification steps should be disabled for the Microsoft 365 account, and please check details in sections below.
-- (Optional) An Azure service principal with necessary permissions. The Azure service principal credentials are required for steps of provision and deploy for Azure based projects.
-
-## Steps
-After the pre-cooked pipelines are scaffolded successfully, the following steps are expected to be performed:
-1. Commit and push your project source code to Azure DevOps remote repository, including the CI/CD yml files.
-1. Create corresponding Azure DevOps pipelines by following [Create your first Azure DevOps Pipeline](https://docs.microsoft.com/en-us/azure/devops/pipelines/create-first-pipeline?view=azure-devops&tabs=java%2Ctfs-2018-2%2Cbrowser).
-1. Configure necessary Azure DevOps Pipeline variables if your pipelines require credentials by checking into the yml files.
-1. Trigger your pipelines automatically, manually or do customization (Check the `trigger:` or `pr:` section in yml files to find the triggers). More about triggers in Azure DevOps, refer to [Triggers in Azure pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops).
-
-## Azure DevOps Pipeline Variables 
-Steps to create Pipeline variables in Azure DevOps:
-1. In the Pipeline editing page, click `Variables` on top right and click `New variable`.
-1. Enter Name/Value pair for your variable.
-1. Toggle the checkbox of `Keep this value secret` if necessary.
-1. Click `OK` to create the variable. 
-
-|Name|Description|
-|---|---|
-|AZURE_SERVICE_PRINCIPAL_NAME|The service principal name of Azure used to provision resources.|
-|AZURE_SERVICE_PRINCIPAL_PASSWORD|The password of Azure service principal.|
-|AZURE_SUBSCRIPTION_ID|To identify the subscription in which the resources will be provisioned.|
-|AZURE_TENANT_ID|To identify the tenant in which the subscription resides.|
-|M365_ACCOUNT_NAME|The Microsoft 365 account for creating and publishing the Teams App.|
-|M365_ACCOUNT_PASSWORD|The password of the Microsoft 365 account.|
-|M365_TENANT_ID|To identify the tenant in which the Teams App will be created/published. This value is optional unless you have a multi-tenant account and you want to use another tenant. Read more on [how to find your Microsoft 365 tenant ID](https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-how-to-find-tenant).|
-> Note: Currently, a non-interactive authentication style for Microsoft 365 is used in CI/CD workflows, so please ensure that your Microsoft 365 account has sufficient privileges in your tenant and doesn't have multi-factor authentication or other advanced security features enabled. Please refer to the [Configure Microsoft 365 Credentials](https://github.com/OfficeDev/teamsfx-cli-action/blob/main/README.md#configure-m365azure-credentials-as-github-secret) to make sure you have disabled Multi-factor Authentication and Security Defaults for the credentials used in the workflow.
-
-> Note: Currently, service principal for Azure is used in CI/CD workflows, and to create Azure service principals for use, refer to [here](#how-to-create-azure-service-principals-for-use).
-
-# How to create Azure service principals for use?
-To provision and deploy resources targeting Azure inside CI/CD, you must create an Azure service principal for use.
-
-Briefly, the steps include:
-1. Register an Azure AD application in single tenant, and it requires sufficient permissions in your Azure AD tenant.
-2. Assign a role to your Azure AD application to access your Azure subscription, and `Contributor` role is recommended. 
-3. Create a new Azure AD application secret.
-4. Grab your tenant id, application id(AZURE_SERVICE_PRINCIPAL_NAME), and the secret(AZURE_SERVICE_PRINCIPAL_PASSWORD) for use.
-
-For detailed guidelines, refer to [the official document](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal). There're three ways to create service principal, [Azure portal](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal), [PowerShell](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-authenticate-service-principal-powershell), [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/create-an-azure-service-principal-azure-cli), and you can choose the way you like.
-
-# Additional Notes
-* [Create your first Azure DevOps Pipeline](https://docs.microsoft.com/en-us/azure/devops/pipelines/create-first-pipeline?view=azure-devops&tabs=java%2Ctfs-2018-2%2Cbrowser)
-* [Manage your apps with the Developer Portal for Microsoft Teams](https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/teams-developer-portal)

package/templates/plugins/resource/cicd_v2/azdo/cd.yml

@@ -1,56 +0,0 @@
-{{=<% %>=}}
-# This is just an example workflow for continuous deployment.
-# You should customize it to meet your own requirements.
-trigger:
-# When new commits are pushed onto the main branch.
-- main 
-
-pool:
-  vmImage: ubuntu-latest
-
-steps:
-# Setup environment.
-- task: NodeTool@0
-  inputs:
-    versionSpec: '14.17.0'
-    checkLatest: true
-
-- task: Bash@3
-  env:
-<%#hosting_type_contains_spfx%>
-    M365_ACCOUNT_NAME: $(M365_ACCOUNT_NAME)
-    M365_ACCOUNT_PASSWORD: $(M365_ACCOUNT_PASSWORD)
-    M365_TENANT_ID: $(M365_TENANT_ID)
-<%/hosting_type_contains_spfx%>
-    # To enable M365 account login by environment variables and non-interactive mode.
-    CI_ENABLED: 'true'
-    TEAMSFX_ENV_NAME: <%env_name%>
-  inputs:
-    targetType: 'inline'
-    script: |
-      set -evuxo pipefail
-      
-      # Install the local dev dependency of @microsoft/teamsfx-cli. 
-      # 'npm ci' is used here to install dependencies and it depends on package-lock.json.
-      # If you prefer to use 'npm ci', please make sure to commit package-lock.json first, or just change it to 'npm install'.
-      npm ci
-
-      # Build the project.
-      # The way to build the current project depends on how you scaffold it.
-      # Different folder structures require different commands set.
-      # 'npm ci' may be used here to install dependencies and it depends on package-lock.json.
-      # If you prefer to use 'npm ci', please make sure to commit package-lock.json first, or just change it to 'npm install'.  
-      <%build_script%>
-
-      # Run unit test.
-      # Currently, no opinioned solution for unit test provided during scaffolding, so,
-      # set up any unit test framework you prefer (for example, mocha or jest) and update the commands accordingly in below.
-      # npm run test
-
-  <%#hosting_type_contains_azure%>
-      # Login Azure by service principal
-      npx teamsfx account login azure --service-principal --username $(AZURE_SERVICE_PRINCIPAL_NAME) --password $(AZURE_SERVICE_PRINCIPAL_PASSWORD) --tenant $(AZURE_TENANT_ID)
-  <%/hosting_type_contains_azure%>
-
-      # Deploy to hosting environment.
-      npx teamsfx deploy --env ${TEAMSFX_ENV_NAME}<%#cloud_resources_contains_apim%> --api-version v1 --open-api-document openapi/openapi.json --api-prefix <%api_prefix%><%/cloud_resources_contains_apim%>

package/templates/plugins/resource/cicd_v2/azdo/ci.yml

@@ -1,37 +0,0 @@
-{{=<% %>=}}
-# This is just an example workflow for continuous integration.
-# You should customize it to meet your own requirements.
-pr:
-# When pull requests targeting the dev branch created.
-- dev 
-
-pool:
-  vmImage: ubuntu-latest
-
-steps:
-# Setup environment.
-- task: NodeTool@0
-  inputs:
-    versionSpec: '14.17.0'
-    checkLatest: true
-  
-- task: Bash@3
-  inputs:
-    targetType: 'inline'
-    script: |
-      set -evuxo pipefail
-
-      # This is just an example workflow for continuous integration.
-      # You should customize it to meet your own requirements.
-
-      # Build the project.
-      # The way to build the current project depends on how you scaffold it.
-      # Different folder structures require different commands set.
-      # 'npm ci' may be used here to install dependencies and it depends on package-lock.json.
-      # If you prefer to use 'npm ci', please make sure to commit package-lock.json first, or just change it to 'npm install'.
-      <%build_script%>
-
-      # Run unit test.
-      # Currently, no opinionated solution for unit test provided during scaffolding, so,
-      # set up any unit test framework you prefer (for example, mocha or jest) and update the commands accordingly in below.
-      # npm run test

package/templates/plugins/resource/cicd_v2/azdo/provision.yml

@@ -1,53 +0,0 @@
-{{=<% %>=}}
-# This is just an example workflow for provision.
-# You should customize it to meet your own requirements.
-trigger: none
-# Manually trigger this workflow, and you should pick the right branch.
-
-pool:
-  vmImage: ubuntu-latest
-
-steps:
-# Setup environment.
-- task: NodeTool@0
-  inputs:
-    versionSpec: '14.17.0'
-    checkLatest: true
-
-# Check out
-- checkout: self
-  persistCredentials: true
-
-- task: Bash@3
-  env:
-    M365_ACCOUNT_NAME: $(M365_ACCOUNT_NAME)
-    M365_ACCOUNT_PASSWORD: $(M365_ACCOUNT_PASSWORD)
-    M365_TENANT_ID: $(M365_TENANT_ID)
-    CI_ENABLED: 'true'
-    TEAMSFX_ENV_NAME: <%env_name%>
-  inputs:
-    targetType: 'inline'
-    script: |
-      set -evuxo pipefail
-      
-      # Install the local dev dependency of @microsoft/teamsfx-cli. 
-      # 'npm ci' is used here to install dependencies and it depends on package-lock.json.
-      # If you prefer to use 'npm ci', please make sure to commit package-lock.json first, or just change it to 'npm install'.
-      npm ci
-  <%#hosting_type_contains_azure%>
-  
-      # Login Azure by service principal
-      npx teamsfx account login azure --service-principal --username $(AZURE_SERVICE_PRINCIPAL_NAME) --password $(AZURE_SERVICE_PRINCIPAL_PASSWORD) --tenant $(AZURE_TENANT_ID)
-  <%/hosting_type_contains_azure%>
-
-      # We suggest to do the `teamsfx provision` step manually or in a separate workflow. The following steps are for your reference.
-      # After provisioning, you should commit necessary files under .fx into the repository. 
-      npx teamsfx provision<%#hosting_type_contains_azure%> --subscription $(AZURE_SUBSCRIPTION_ID)<%/hosting_type_contains_azure%> --env ${TEAMSFX_ENV_NAME}<%#cloud_resources_contains_sql%> --sql-admin-name $(SQL_ADMIN_NAME) --sql-password $(SQL_PASSWORD)<%/cloud_resources_contains_sql%>
-
-      # Commit provision configs if necessary.
-      # To enable scripts to run git commands, check https://docs.microsoft.com/en-us/azure/devops/pipelines/scripts/git-commands?view=azure-devops&tabs=yaml
-      git config user.name "azdo-agent"
-      git config user.email "azdo-agent@azure.com"
-      git add .
-      git commit -m "chore: commit provision configs"
-      git push origin HEAD:${BUILD_SOURCEBRANCHNAME}

package/templates/plugins/resource/cicd_v2/azdo/publish.yml

@@ -1,45 +0,0 @@
-{{=<% %>=}}
-# This is just an example workflow for publishing Teams app.
-# You should customize it to meet your own requirements.
-trigger: none
-# Manually trigger this workflow, and you should pick the right branch.
-
-pool:
-  vmImage: ubuntu-latest
-
-steps:
-# Setup environment.
-- task: NodeTool@0
-  inputs:
-    versionSpec: '14.17.0'
-    checkLatest: true
-
-- task: Bash@3
-  env:
-    M365_ACCOUNT_NAME: $(M365_ACCOUNT_NAME)
-    M365_ACCOUNT_PASSWORD: $(M365_ACCOUNT_PASSWORD)
-    M365_TENANT_ID: $(M365_TENANT_ID)
-    # To enable M365 account login by non-interactive mode. 
-    CI_ENABLED: 'true'
-    TEAMSFX_ENV_NAME: <%env_name%>
-  inputs:
-    targetType: 'inline'
-    script: |
-      set -evuxo pipefail
-      
-      # Install the local dev dependency of @microsoft/teamsfx-cli. 
-      # 'npm ci' is used here to install dependencies and it depends on package-lock.json.
-      # If you prefer to use 'npm ci', please make sure to commit package-lock.json first, or just change it to 'npm install'.
-      npm ci
-
-      # This step is to pack the Teams App as zip file,
-      # which can be used to be uploaded onto Teams Client for installation.
-      # Build Teams App's Package.
-      npx teamsfx package --env ${TEAMSFX_ENV_NAME}
-
-      # Upload Teams App's Package as artifacts.
-      # Choose what your workflow/pipeline platform provided to
-      # upload build/appPackage/appPackage.staging.zip as artifacts.
-
-      # Publish Teams App.
-      npx teamsfx publish --env ${TEAMSFX_ENV_NAME} 

package/templates/plugins/resource/cicd_v2/github/README.md

@@ -1,48 +0,0 @@
-# How to use pre-cooked workflows on GitHub
-
-## Prerequisites
-- Teams app projects are version controlled by GitHub.
-- (Optional) An Microsoft 365 account. If you do not have Microsoft 365 account, apply one from [Microsoft 365 developer program](https://developer.microsoft.com/en-us/microsoft-365/dev-program). The Microsoft 365 account credentials are required for steps of provision, publish and deployment for SPFx projects. Any extra interactive verification steps should be disabled for the Microsoft 365 account, and please check details in sections below.
-- (Optional) An Azure service principal with necessary permissions. The Azure service principal credentials are required for steps of provision and deploy for Azure based projects.
-
-## Steps
-After the pre-cooked workflows are scaffolded successfully, the following steps are expected to be performed:
-1. Commit and push your project source code to GitHub remote repository, including the CI/CD yml files.
-1. Configure necessary GitHub secrets if your workflows require credentials by checking into the yml files.
-1. Trigger your workflows automatically, manually or do customization (Check the `on:` section in yml files to find the triggers). More about triggers in GitHub, refer to [trigger a workflow](https://docs.github.com/en/actions/using-workflows/triggering-a-workflow).
-
-## GitHub Secrets 
-Steps to create secrets by environment in GitHub (Environment feature is not available in Private repositories.):
-1. In the project `Settings` page, navigate to `Environments` section and click `New environment`.
-1. Enter a name for your environment. The default environment name provided in the template is `test_environment`. Click `Configure environment` to proceed.
-1. In the next page, click `Add Secret` to add secrets for each of the items listed in the table below.
-
-Or create repository secrets by follow the path of `Settings` > `Security` > `Secrets` > `Actions` > `New repository secret`.
-
-|Name|Description|
-|---|---|
-|AZURE_SERVICE_PRINCIPAL_NAME|The service principal name of Azure used to provision resources.|
-|AZURE_SERVICE_PRINCIPAL_PASSWORD|The password of Azure service principal.|
-|AZURE_SUBSCRIPTION_ID|To identify the subscription in which the resources will be provisioned.|
-|AZURE_TENANT_ID|To identify the tenant in which the subscription resides.|
-|M365_ACCOUNT_NAME|The Microsoft 365 account for creating and publishing the Teams App.|
-|M365_ACCOUNT_PASSWORD|The password of the Microsoft 365 account.|
-|M365_TENANT_ID|To identify the tenant in which the Teams App will be created/published. This value is optional unless you have a multi-tenant account and you want to use another tenant. Read more on [how to find your Microsoft 365 tenant ID](https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-how-to-find-tenant).|
-> Note: Currently, a non-interactive authentication style for Microsoft 365 is used in CI/CD workflows, so please ensure that your Microsoft 365 account has sufficient privileges in your tenant and doesn't have multi-factor authentication or other advanced security features enabled. Please refer to the [Configure Microsoft 365 Credentials](https://github.com/OfficeDev/teamsfx-cli-action/blob/main/README.md#configure-m365azure-credentials-as-github-secret) to make sure you have disabled Multi-factor Authentication and Security Defaults for the credentials used in the workflow.
-
-> Note: Currently, service principal for Azure is used in CI/CD workflows, and to create Azure service principals for use, refer to [here](#how-to-create-azure-service-principals-for-use).
-
-# How to create Azure service principals for use?
-To provision and deploy resources targeting Azure inside CI/CD, you must create an Azure service principal for use.
-
-Briefly, the steps include:
-1. Register an Azure AD application in single tenant, and it requires sufficient permissions in your Azure AD tenant.
-1. Assign a role to your Azure AD application to access your Azure subscription, and `Contributor` role is recommended. 
-1. Create a new Azure AD application secret.
-1. Grab your tenant id, application id(AZURE_SERVICE_PRINCIPAL_NAME), and the secret(AZURE_SERVICE_PRINCIPAL_PASSWORD) for use.
-
-For detailed guidelines, refer to [the official document](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal). There're three ways to create service principal, [Azure portal](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal), [PowerShell](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-authenticate-service-principal-powershell), [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/create-an-azure-service-principal-azure-cli), and you can choose the way you like.
-
-# Additional Notes
-* [Quick Start for GitHub Actions](https://docs.github.com/en/actions/quickstart#creating-your-first-workflow)
-* [Manage your apps with the Developer Portal for Microsoft Teams](https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/teams-developer-portal)