Introduce a version check mechanism

Author: devanshjainms

.github/workflows/codeql.yml

@@ -43,7 +43,7 @@ jobs:
           egress-policy: audit
 
       - name: Checkout repository
-        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
 
       - name: Initialize CodeQL
         uses: github/codeql-action/init@5d4e8d1aca955e8d8589aabd499c5cae939e33c7 # v4.31.9

.github/workflows/dependency-review.yml

@@ -22,6 +22,6 @@ jobs:
           egress-policy: audit
 
       - name: 'Checkout Repository'
-        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
       - name: 'Dependency Review'
         uses: actions/dependency-review-action@3b139cfc5fae8b618d3eae3675e383bb1769c019 # v4.5.0

.github/workflows/github-actions-ansible-lint.yml

@@ -14,10 +14,10 @@ jobs:
           egress-policy: audit
 
       - name: Checkout the code
-        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
 
       - name: Setup Python
-        uses: actions/setup-python@42375524e23c412d93fb67b49958b491fce71c38 #v5.4.0
+        uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 #v6.2.0
         with:
           python-version: '3.10'
 

.github/workflows/github-actions-code-coverage.yml

@@ -14,10 +14,10 @@ jobs:
           egress-policy: audit
 
       - name: Checkout the code
-        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 #v6.0.1
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd #v6.0.2
 
       - name: Setup Python
-        uses: actions/setup-python@42375524e23c412d93fb67b49958b491fce71c38 #v5.4.0
+        uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 #v6.2.0
         with:
           python-version: '3.10'
 

.github/workflows/ossf-scoreboard.yml

@@ -31,7 +31,7 @@ jobs:
           egress-policy: audit
 
       - name: "Checkout code"
-        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
         with:
           persist-credentials: false
 

.github/workflows/trivy.yml

@@ -23,7 +23,7 @@ jobs:
         egress-policy: audit
 
     - name: Checkout code
-      uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
+      uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
 
     - name: Run Trivy vulnerability scanner (file system)
       uses: aquasecurity/trivy-action@18f2510ee396bbf400402947b394f2dd8c87dbb0 # 0.29.0

WORKSPACES/SYSTEM/DEV-WEEU-SAP01-X00/sap-parameters.yaml

@@ -24,6 +24,8 @@ db_instance_number:            "00"
 platform:                      HANA
 database_high_availability:    true
 database_cluster_type:         AFA
+# database scale out
+database_scale_out :           false
 
 #############################################################################
 #                              Storage Profile                              #
@@ -42,3 +44,9 @@ secret_id:                     https://<key-vault-name>.vault.azure.net/secrets/
 # The MSI Client ID is used to authenticate to Azure services
 # and is required if the management server uses user assigned managed identity
 user_assigned_identity_client_id: "00000000-0000-0000-0000-000000000000"
+
+#############################################################################
+#                        ANF Parameters (optional)                           #
+#############################################################################
+ANF_account_rg:                "ANF-RESOURCE-GROUP"
+ANF_account_name:              "ANF-ACCOUNT-NAME"

docs/SETUP.MD

@@ -198,9 +198,16 @@ telemetry_data_destination: "azureloganalytics"
 telemetry_table_name: "your-telemetry-table-name"
 
 # The workspace id, shared key of the Log Analytics workspace.
+# If laws_shared_key is not provided, it will be auto-fetched from Azure using the parameters below.
 laws_shared_key: "your-log-analytics-shared-key"
 laws_workspace_id: "your-log-analytics-workspace-id"
 
+# Optional: Azure subscription and resource details for auto-fetching Log Analytics shared key.
+# Required when laws_shared_key is not provided.
+laws_subscription_id: "your-laws-subscription-id"
+laws_resource_group: "your-laws-resource-group"
+laws_workspace_name: "your-laws-workspace-name"
+
 # The cluster name, data ingestion URI, and client ID of the Azure Data Explorer.
 adx_cluster_fqdn: "your-adx-cluster-fqdn"
 adx_database_name: "your-adx-database-name"
@@ -280,6 +287,7 @@ db_sid: "your-db-sid"
 # Boolean indicating if the SCS and database is configured as highly available.
 scs_high_availability: true
 database_high_availability: true
+database_scale_out : false  # true if database high availability is configured as scale-out
 
 # The high availability configuration of the SCS and DB instance. Supported values are:
 # - AFA (for Azure Fencing Agent)

docs/TELEMETRY_SETUP.md

@@ -74,5 +74,9 @@ This guide outlines the steps to create an Azure Data Explorer (Kusto) cluster a
 
 5. **Parameters**
     - **laws_workspace_id:** Log Analytics Workspace ID [Workspace ID]
-    - **laws_shared_key:** Log Analytics Shared Key [Primary Key]
+    - **laws_shared_key:** Log Analytics Shared Key [Primary Key, if available]
+    - **laws_subscription_id:** Subscription ID where the Log Analytics Workspace is created
+    - **laws_resource_group:** Resource Group name where the Log Analytics Workspace is created
+    - **laws_workspace_name:** Log Analytics Workspace name
     - **telemetry_table_name:** Name of the table in Log Analytics SAP_AUTOMATION_QA
+    - **user_assigned_identity_client_id:** User Assigned Managed Identity Client ID (optional, required if using UAMI for authentication)

requirements.in

@@ -8,6 +8,7 @@ azure-identity
 azure-kusto-data
 azure-kusto-ingest
 azure-mgmt-compute
+azure-mgmt-loganalytics
 azure-mgmt-network
 azure-storage-blob
 azure-storage-queue