Cut 4960 eu tenant support

[gweinjc]

Issues

• CUT-4960 - EU Tenant Support

What does this solve?

This pull request focuses on improving consistency, clarity, and maintainability across the CI workflow, editor configuration, and PowerShell scripts. The most significant changes include standardizing naming conventions, specifying dependency versions, enhancing support for EU testing, updating editor and formatting settings, and refactoring PowerShell scripts for better readability and reliability.

Main Changes:

• Added -JCEnvironment param to Connect-JCOnline and Set-JCSettingsFile functions to allow for admins to change their environment from 'STANDARD' to 'EU'
• Updated the Settings file to include a configurable JCEnvironment.Location value

Other Changes:

CI Workflow and Dependency Management:

• Standardized naming from Dependancies to Dependencies throughout the .github/workflows/powershell-module-ci.yml file, including job names, cache keys, and dependencies lists. This improves clarity and consistency in the CI pipeline. [1] [2] [3] [4] [5] [6] [7] [8] [9]
• Updated required versions for JumpCloud.SDK.V1, JumpCloud.SDK.V2, and JumpCloud.SDK.DirectoryInsights modules from latest to 0.1.1, ensuring reproducible builds and reducing risk of breaking changes from upstream updates.

EU Testing Support:

• Added new environment variables (PESTER_EU_APIKEY, PESTER_EU_ORGID) and corresponding PowerShell global variables to enable Pester testing for EU organizations, expanding test coverage. [1] [2]

Editor and Formatting Configuration:

• Updated .vscode/settings.json to use the correct cSpell.enabledFileTypes format and added extensive PowerShell formatting options, improving code quality and consistency for contributors. [1] [2]

PowerShell Script Refactoring:

• Refactored Build-HelpFiles.ps1 to use consistent lowercase keywords (param, try, catch, if, switch, foreach, default), added status output for help file generation steps, and enabled PlatyPS logging for better traceability and error handling. [1] [2] [3] [4] [5] [6] [7] [8] [9]
• Improved filtering logic in jcapiToSupportSync.ps1 to exclude additional unwanted parameters (apiHost, consoleHost), and standardized PowerShell keyword casing for better readability and maintainability. [1] [2] [3]

Is there anything particularly tricky?

• This requires the v0.1.1 versions of the SDKs, which are currently hidden

How should this be tested?

1. Install the latest versions of the SDKs

Install-Module -Name JumpCloud.SDK.DirectoryInsights -RequiredVersion 0.1.1 -Force
Install-Module -Name JumpCloud.SDK.V1 -RequiredVersion 0.1.1 -Force
Install-Module -Name JumpCloud.SDK.V2 -RequiredVersion 0.1.1 -Force

2. Import the Module

Import-Module “/Users/USERNAME/Documents/GitHub/support/PowerShell/JumpCloud Module/JumpCloud.psd1” -force

3. Attempt to connect to an EU organization via Connect-JCOnline

### Connect to EU Org
Connect-JCOnline -JumpCloudApiKey 'EUAPIKEY' -JCEnvironment 'EU'

### Get a user to validate that it works
Get-JCUser | Select -First 1

4. Close your terminal and reopen and run Connect-JCOnline as you would normally

Import-Module “/Users/USERNAME/Documents/GitHub/support/PowerShell/JumpCloud Module/JumpCloud.psd1” -force
Connect-JCOnline -JumpCloudApiKey 'EUAPIKEY'

### Get a user to validate that it works
Get-JCUser | Select -First 1

5. Close your terminal again and reopen and run the following to change to standard

Import-Module “/Users/USERNAME/Documents/GitHub/support/PowerShell/JumpCloud Module/JumpCloud.psd1” -force
Set-JCSettingsFile -JCEnvironmentLocation 'STANDARD'
Connect-JCOnline -JumpCloudApiKey 'USAPIKEY'

### Get a user to validate that it works
Get-JCUser | Select -First 1

[kmaranionjc]

Looks good on my end. Great work here!