name: test  # this line is optional and should only be present if the used specified the name option. Otherwise we should remove it and don't specify any name. In that case Azure DevOps generates default naming based on date and run number.

trigger:
  branches:
    include:
      - main # depends on what user passed in option branchName. default is main

pool:
  vmImage: "ubuntu-latest"

variables:
  - name: CertificateBase64Encoded # this should be visible only when application login method was used which is the default one.
    value: "" # this should be filled manually by the user
  - name: CertificateSecureFileId # this should be visible only when application login method was used which is the default one
    value: "" # this should be filled manually by the user
  - name: CertificatePassword # this should be visible only when application login method was used which is the default one
    value: "" # this should be filled manually by the user
  - name: EntraIDAppId # this should be visible only when application login method was used which is the default one
    value: "" # this should be filled manually by the user
  - name: UserName # this should be visible only when user login method was used
    value: "" # this should be filled manually by the user
  - name: Password # this should be visible only when user login method was used
    value: "" # this should be filled manually by the user
  - name: TenantId
    value: "2942bb31-1d49-4da6-8d3d-d0f9e1141486" # I think we should be able to retrive that and prefil. But only if the user is logged in as the spfx commands do not require being logged in to m365 tenant
  - name: SharePointBaseUrl
    value: "https://tenanttocheck.sharepoint.com"  # I think we should be able to retrive that and prefil. But only if the user is logged in as the spfx commands do not require being logged in to m365 tenant
  - name: PackageName
    value: "demo-1.sppkg" # we should prefil that
  - name: SiteAppCatalogUrl # this option and it's value should only be present in the flow if the siteUrl option was used in the command
    value: "https://tenanttocheck.sharepoint.com/sites/PnPDemo2/AppCatalog"

stages:
  - stage: "Build_and_Deploy"
    jobs:
      - job: "Build_and_Deploy"
        steps:
          - task: NodeTool@0
            displayName: "Use Node.js"
            inputs:
              versionSpec: "18.x"

          - task: Npm@1
            displayName: "Run npm install"
            inputs:
              command: "install"

          - task: Gulp@0
            displayName: "Gulp bundle"
            inputs:
              gulpFile: ./gulpfile.js
              targets: bundle
              arguments: "--ship"

          - task: Gulp@0
            displayName: "Gulp package"
            inputs:
              targets: "package-solution"
              arguments: "--ship"

          - task: Npm@1
            displayName: "Install CLI for Microsoft 365"
            inputs:
              command: custom
              verbose: false
              customCommand: "install -g @pnp/cli-microsoft365"

          - script: |
              m365 login --authType certificate --certificateBase64Encoded "$(CertificateBase64Encoded)" --password "$(CertificatePassword)" --appId "$(EntraIDAppId)" --tenant "$(TenantId)"
              m365 spo set --url "$(SharePointBaseUrl)"
              m365 spo app add --filePath "$(Build.SourcesDirectory)/sharepoint/solution/$(PackageName)" --overwrite
              m365 spo app deploy --name "$(PackageName)" --appCatalogScope sitecollection --appCatalogUrl "($SiteAppCatalogUrl)"
            displayName: "CLI for Microsoft 365 Deploy App"

           # if the site scop was set and the siteUrl option was set we should replace the m365 spo app add command so that it targets siteAppCatalog like
           # m365 spo app add --filePath "$(Build.SourcesDirectory)/sharepoint/solution/$(PackageName)" --appCatalogScope sitecollection --appCatalogUrl "($SiteAppCatalogUrl)" 

          # if skipFeatureDeployment option was set then the m365 spo app deploy command in hte aboce script should have an --skipFeatureDeployment flag as well
          
          # if user login method was used in the command then we should replace the m365 login command in the above script with this one (along with the variables which are present in the upper part of the yaml pipeline
          # m365 login --authType password --userName "$(UserName)" --password "$(Password)"