v1.9.3 - Configurable VPN Output Path

Enhancement: Configurable VPN Output Path

Added configurable path for VPN configuration output, replacing hardcoded script-relative directory with a user-configurable option in config.json.

New Features

• Configurable VPN Output Directory
  • Added paths.vpnOutputPath to config.json for customizable VPN config storage location
  • VPN configurations can now be saved to any user-specified directory
  • Example: "vpnOutputPath": "C:\Users\Username\Documents\VPN"
  • Allows organizing VPN configs separately from application directory

Enhancements

• Improved Architecture
  • Removes the only directory creation tied to $PSScriptRoot
  • Clean separation of application and user data directories
  • More flexible for different deployment scenarios

Backward Compatibility

• Fully Backward Compatible
  • Existing configs without vpnOutputPath continue to work
  • Falls back to script directory (vpn_output/) if not configured
  • No breaking changes - optional enhancement only

Config Changes

New Configuration Field:

"paths": {
  "vpnOutputPath": "C:\path\to\vpn_output"
}

Note: This field is optional. If not present in your config, VPN configs will save to the script directory as before.

Technical Details

• Updated Get-VpnConnections function to check for configured path
• Added graceful fallback for backward compatibility
• Updated config.example.json with new field and documentation

---

Full Changelog: v1.9.2...v1.9.3