When removing 1 connection and there are only 2 connections within the configuration file the config file is removed.
Expected Behavior
The last remaining connections should be re-written to the config file
Current Behavior
when the connections count is 2 the file is just removed. if the connections count is > 2 then the removal works as expected
Possible Solution
Change the Line 73 in Remove-FreshServiceConnection.ps1
Current
if ($environments.Count -gt 0) {
NEW
if (($environment) -or ($environment.count -gt 0)) {
Steps to Reproduce (for bugs)
- New-FreshServiceConnection -Name "acme1" -ApiKey "acme1" -Tenant 'acme1' -Environment Sandbox
- New-FreshServiceConnection -Name "acme2" -ApiKey "acme2" -Tenant 'acme2' -Environment Sandbox
- Remove-FreshServiceConnection -Name "acme2"
Context
when preforming removal of the sandbox API connection you have to redefine the production connection. More of an Annoyance.
Your Environment
- Module version used: 0.1.6
- Operating System and PowerShell version:
Windows 11 23H2
PS Version 5.1.22621.4111
When removing 1 connection and there are only 2 connections within the configuration file the config file is removed.
Expected Behavior
The last remaining connections should be re-written to the config file
Current Behavior
when the connections count is 2 the file is just removed. if the connections count is > 2 then the removal works as expected
Possible Solution
Change the Line 73 in Remove-FreshServiceConnection.ps1
Current
if ($environments.Count -gt 0) {
NEW
if (($environment) -or ($environment.count -gt 0)) {
Steps to Reproduce (for bugs)
Context
when preforming removal of the sandbox API connection you have to redefine the production connection. More of an Annoyance.
Your Environment
Windows 11 23H2
PS Version 5.1.22621.4111