ci: add azdo

Author: parisb

.azdo/pr.yaml

@@ -0,0 +1,99 @@
+trigger: none
+
+resources:
+  containers:
+    - container: 'sonarscan'
+      image: 'sonarsource/sonarcloud-scan'
+  repositories:
+    - repository: pipelineTemplates
+      type: git
+      name: "PLT.INFRA.PIPELINES/PLT.INFRA.PIPELINES"
+      ref: "refs/heads/main"
+
+variables:
+  orgName:  'parisbrooker-iac'
+stages:
+  - stage: entry_criteria
+    displayName: "[STAGE] Entry Criteria"
+    jobs:
+      - template: "/jobs/precommit_checks_job.yaml@pipelineTemplates"
+      - template: "/jobs/commitlint_lint_job.yaml@pipelineTemplates"
+  - stage: 'stage_test_build'
+    displayName: '[STAGE] Test and Build'
+    variables:
+      GOVERSION: '1.23.5'   # Version of Go tools used for building and testing
+      CGO_ENABLED: '0'      # Disable cgo to get a static binary
+      GOOS: 'linux'
+      GOARCH: 'amd64'
+    jobs:
+
+    - job: job_go_test_build
+      displayName: '[JOB] Test and Build'
+      pool:
+        vmImage: 'ubuntu-latest'
+
+      steps:
+      - checkout: self
+        fetchDepth: 0
+
+      - task: GoTool@0
+        displayName: '[TOOLS] Install Go $(GOVERSION)'
+        inputs:
+          version: $(GOVERSION)
+
+      - task: UseDotNet@2
+        displayName: '[TOOLS] Install .NET Core sdk 8.0.x'
+        inputs:
+          version: 8.0.x
+
+      - script: |
+          sh -c "$(curl --location https://taskfile.dev/install.sh)" -- -d -b ~/.local/bin
+        name: taskfile
+        displayName: '[TOOLS] Install Taskfile'
+
+      - task: SonarCloudPrepare@3
+        displayName: '[SCAN] Prepare analysis configuration'
+        inputs:
+          SonarCloud: 'testing'
+          organization: 'parisbrooker-iac'
+          scannerMode: 'CLI'
+          projectKey: parisbrooker-iac_rp.plt.product.tmpltr
+          projectName: rp.plt.product.tmpltr
+
+      - script: |
+          # Get tools for converting Go's test reports
+          curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s -- -b $(go env GOPATH)/bin v1.63.4
+          ~/.local/bin/task get_test_dependencies
+          ~/.local/bin/task test_coverage
+          $HOME/go/bin/golangci-lint run ./...
+
+        displayName: '[TEST] Go Test'
+        failOnStderr: false
+
+      - script: |
+          ~/.local/bin/task build
+        displayName: '[BUILD] Go Binary'
+
+      - task: SonarCloudAnalyze@3
+        displayName: '[SCAN] Run SonarCloud analysis'
+
+      - task: SonarCloudPublish@3
+        displayName: '[SCAN] Publish results on build summary'
+
+      - task: reportgenerator@5
+        displayName: '[TEST] Generate Report'
+        inputs:
+          reports: 'coverage.xml'
+          reportTypes: "HtmlInline_AzurePipelines_Dark;Cobertura"
+          publishCodeCoverageResults: true
+
+      - task: PublishTestResults@2
+        displayName: '[TEST] Publish Test Results'
+        inputs:
+          testRunner: JUnit
+          testResultsFiles: $(Build.SourcesDirectory)/report.xml
+          searchFolder: $(Build.SourcesDirectory)
+
+      - publish: '$(Build.SourcesDirectory)/bin/tmpltr'
+        artifact: 'Executable'
+        displayName: '[BUILD] Publish pipeline artifact'

.github/copilot-instructions.md

@@ -2,14 +2,21 @@
 
 <!-- Testing -->
 
-When generating unit tests for go, use table-driven tests where appropriate and always use the arrange, act, assert pattern and indicate these "regions" with comments, even if there is nothing to do in that region.
+When generating unit tests for go, use table-driven tests where appropriate and always use the arrange, act, assert pattern and indicate these
+"regions" with comments, even if there is nothing to do in that region.
+
+When testing the parsing or manipulation of config files (yaml, json, toml), always embed a literal document in the test case itself. Rather than being arbitrary values, they should be like configurations as they would be in normal use of the application.
+
+When testing unexported methods or functions, these tests should be created in a file called `export_test.go` in the same package as the tested method or function.
 
 Wherever the tested method or function uses the afero package, always use a memmap fs as the filesystem in tests (i.e. don't write to disk where this can be avoided.).
 
 When writing assertions in tests, do not abstract assertion/verification logic into functions stores in test cases, explicitly define the assertion or verification logic in the "Assert" portion of the test; use conditional logic if needed here.
 
 When creating a test file, the package name should always be the package name with "\_test" appended.
 
+When creating or satisfying a slog logger on services, always use the DiscardHandler
+
 <!-- Style -->
 
 Any comments you include above functions or types should end with a period.

.golangci.yml

@@ -344,7 +344,7 @@ linters:
     nolintlint:
       # Exclude following linters from requiring an explanation.
       # Default: []
-      allow-no-explanation: [funlen, gocognit, golines, mnd]
+      allow-no-explanation: [funlen, gocognit, golines, mnd, nestif]
       # Enable to require an explanation of nonzero length after each nolint directive.
       # Default: false
       require-explanation: true