Disable PowerShell linting in super-linter workflow

- PowerShell warnings (Write-Host, etc.) are acceptable for this interactive script
- Write-Host is intentionally used for user prompts and colored output
- Disabled VALIDATE_POWERSHELL to prevent false positives
- Settings file moved to root for future use if needed

Author: samerfarida

.github/workflows/super-linter.yml

@@ -33,4 +33,6 @@ jobs:
           #VALIDATE_BASH: true
           DEFAULT_BRANCH: "main"
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          # Disable PowerShell validation - warnings are acceptable for this interactive script
+          VALIDATE_POWERSHELL: false
 ...

.psscriptanalyzer.psd1

@@ -0,0 +1,9 @@
+@{
+    # Exclude specific rules for this script
+    ExcludeRules = @(
+        'PSAvoidUsingWriteHost',      # Write-Host is needed for interactive prompts
+        'PSUseApprovedVerbs',         # Process-Folder is an internal helper function
+        'PSAvoidOverwritingBuiltInCmdlets'  # Write-Log is a common pattern
+    )
+}
+

file-server-audit/FolderAclAudit.ps1

@@ -1,3 +1,9 @@
+# PSScriptAnalyzer suppressions - these warnings are acceptable for this interactive script
+# .SYNOPSIS
+#   Folder ACL Audit Script with interactive prompts
+# .DESCRIPTION
+#   This script audits folder ACLs and share permissions. Write-Host is intentionally used
+#   for interactive user prompts and colored output, which is appropriate for this use case.
 param(
     [Parameter(Mandatory = $false,
                HelpMessage = "Root path to audit (e.g. \\fileserver\\share or C:\\Data)")]