Merge branch 'main' into sylvainsf-pr-format-check

.github/ISSUE_TEMPLATE/bug.yaml

@@ -0,0 +1,71 @@
+name: Bug Report
+description: Report broken functionality within Radius
+title: "<BUG TITLE>"
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: "## Bug information"
+  - type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: How can we recreate this bug? Be specific.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Observed behavior
+      description: What you're experiencing that you believe is a bug.
+      placeholder: |
+        If applicable, add screenshots to help explain your problem.
+
+        Tip: You can attach images or files by clicking this area to highlight it and then dragging files in.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Desired behavior
+      description: What you're expecting to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Workaround
+      description: Have you found a workaround to get you unblocked?
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: "## System information"
+  - type: textarea
+    attributes:
+      label: rad Version
+      description: What rad cli version are you running?
+      placeholder: PASTE OUTPUT OF "rad version"
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Operating system
+      description: What operating system (macOS Monterey, Windows 11, etc.) and architecture (x86, x64, arm64, etc.) are you running?
+      placeholder: |
+        For example: macOS Monterey, M1 chip
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add any other context about the problem here.
+      placeholder: |
+        Links? References? Anything that will give us more context about the issue you are encountering!
+
+        Tip: You can attach images or files by clicking this area to highlight it and then dragging files in.
+    validations:
+      required: false
+  - type: checkboxes
+    attributes:
+      label: Would you like to support us?
+      description: Would you like to support us in fixing this bug?
+      options:
+        - label: Yes, I would like to support you
+          required: false

.github/ISSUE_TEMPLATE/engineering.yaml

@@ -0,0 +1,71 @@
+name: Engineering Improvement
+description: Report problems or suggestions to improve the Radius engineering processes and/or pipelines
+title: "<TITLE>"
+labels: ["maintenance"]
+body:
+  - type: markdown
+    attributes:
+      value: "## Engineering Improvement"
+  - type: textarea
+    attributes:
+      label: Area for Improvement
+      description: What engineering process or tools can be improved? Build? Testing? ...? Be specific.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Observed behavior
+      description: What you're experiencing that you believe could be improved.
+      placeholder: |
+        If applicable, add screenshots to help explain your problem.
+
+        Tip: You can attach images or files by clicking this area to highlight it and then dragging files in.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Desired behavior
+      description: What you'd like to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Proposed Fix
+      description: Have you found a way to implement or fix the issue?
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: "## System information"
+  - type: textarea
+    attributes:
+      label: rad Version
+      description: What rad cli version are you running?
+      placeholder: PASTE OUTPUT OF "rad version"
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Operating system
+      description: What operating system (macOS Monterey, Windows 11, etc.) and architecture (x86, x64, arm64, etc.) are you running?
+      placeholder: |
+        For example: macOS Monterey, M1 chip
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add any other context about the problem here
+      placeholder: |
+        Links? References? Anything that will give us more context about the issue you are encountering!
+
+        Tip: You can attach images or files by clicking this area to highlight it and then dragging files in.
+    validations:
+      required: false
+  - type: checkboxes
+    attributes:
+      label: Would you like to support us?
+      description: Would you like to support us in improving Radius engineering processes and/or pipelines?
+      options:
+        - label: Yes, I would like to support you
+          required: false

.github/ISSUE_TEMPLATE/feature.yaml

@@ -0,0 +1,34 @@
+name: Feature Request
+description: Request a feature in Radius
+title: "<FEATURE TITLE>"
+labels: ["feature"]
+body:
+  - type: textarea
+    attributes:
+      label: Overview of feature request
+      description: What are you proposing Radius add/update/remove?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Acceptance criteria
+      description: What will need to be completed/working for this feature to be marked "Done"?
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add any other context about the problem here
+      placeholder: |
+        Links? References? Anything that will give us more context about the feature you are looking for!
+
+        Tip: You can attach images or files by clicking this area to highlight it and then dragging files in.
+    validations:
+      required: false
+  - type: checkboxes
+    attributes:
+      label: Would you like to support us?
+      description: Would you like to support us in implementing the feature?
+      options:
+        - label: Yes, I would like to support you
+          required: false

.github/workflows/build.yaml

@@ -35,7 +35,7 @@ concurrency:
 
 env:
   # Go version to install
-  GOVER: '^1.21'
+  GOVER: '1.21.7'
 
   # gotestsum version - see: https://github.com/gotestyourself/gotestsum
   GOTESTSUMVERSION: 1.10.0

.github/workflows/close-stale-prs.yml

@@ -0,0 +1,27 @@
+# This workflow warns and then closes PRs that have had no activity for 90 days.
+#
+# For more information, see:
+# https://github.com/actions/stale
+name: Close stale pull requests
+
+on:
+  schedule:
+  - cron: '0 18 * * *' # Run the workflow every day at 6PM UTC (10AM PST).
+
+jobs:
+  stale:
+
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
+
+    steps:
+    - uses: actions/stale@v5
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        stale-pr-message: 'This pull request has been automatically marked as stale because it has been inactive for 90 days. Remove stale label or comment or this PR will be closed in 7 days.'
+        stale-pr-label: 'stale'
+        days-before-pr-stale: 90 # 3 months
+        days-before-pr-close: 7
+        days-before-issue-stale: -1
+        days-before-issue-close: -1

.github/workflows/functional-test.yaml

@@ -31,7 +31,7 @@ on:
 
 env:
   # Go version
-  GOVER: '^1.21'
+  GOVER: '1.21.7'
   GOPROXY: https://proxy.golang.org
 
   # gotestsum version - see: https://github.com/gotestyourself/gotestsum
@@ -576,6 +576,28 @@ jobs:
         with:
           name: ${{ matrix.name }}_container_logs
           path: ./${{ env.RADIUS_CONTAINER_LOG_BASE }}
+      - name: Get Terraform recipe publishing logs
+        if: always()
+        run: |
+          # Create pod-logs directory
+          mkdir -p recipes/pod-logs
+          # Get pod logs and save to file
+          namespace="radius-test-tf-module-server"
+          label="app.kubernetes.io/name=tf-module-server"
+          pod_names=($(kubectl get pods -l $label -n $namespace -o jsonpath='{.items[*].metadata.name}'))
+          for pod_name in "${pod_names[@]}"; do
+            kubectl logs $pod_name -n $namespace > recipes/pod-logs/${pod_name}.txt
+          done
+          echo "Pod logs saved to recipes/pod-logs/"
+          # Get kubernetes events and save to file
+          kubectl get events -n $namespace > recipes/pod-logs/events.txt
+      - name: Upload Terraform recipe publishing logs 
+        uses: actions/upload-artifact@v3
+        if: always()
+        with:
+          name: recipes-pod-logs
+          path: recipes/pod-logs
+          if-no-files-found: error
       - uses: marocchino/sticky-pull-request-comment@v2
         if: success() && env.PR_NUMBER != ''
         continue-on-error: true

.github/workflows/lint.yaml

@@ -33,7 +33,7 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 30
     env:
-      GOVER: '^1.21'
+      GOVER: '1.21.7'
       GOPROXY: https://proxy.golang.org
       HELM_CHARTS_DIR: deploy/Chart
     steps: