Tentacle Cloner Fix for Trailing Slashes

This release closes issue #42, where the tentacle cloner didn't like trailing slashes in the URI.

Adding Support for 2022.3 and 2022.4

Minor bug fixes to add support for 2022.3 and 2022.4.

• Target model wasn't returning a status property to set, added a check to ensure the property is there
• If a variable is a certificate type but doesn't have an assigned certificate, the cloner will throw a random null reference error. It will now throw a specific error so you can fix the data.

Bug Fixes for cloning step templates

This release fixes a few bugs that might occur when cloning step templates

• #39 Community Step Templates now work when running in what-if mode
• #40 Step templates with a package feed id containing not-existing are converted to null prior to saving.

Project Variable Template Cloning

This release fixes issue #36. Previously, if you had a pre-existing project and you added a new project variable template, that template was not getting copied over. That has now been fixed, project variable templates are copied over for both existing and new projects.

Support for PowerShell 5.1 on the clone tentacle instance script

The clone tentacle instance script didn't work when it was run using PowerShell 5.1. There was a check to see if the OS was Windows using the $IsWindows built-in variable, and if it was then set some paths.

However, $IsWindows was added in PowerShell 6. Instead, we flipped the check to see if $IsLinux was set. If it was set to $true then set the paths to Linux. If it was $false or $null (it would be null in PS 5.1 and lower), then assume it was Windows.

Deploy a release step support

This release adds support for the deploy a release step.

1. Any deployment or runbook process that uses the deploy a release step will have the project id successfully converted (fixing issue #34).
2. In the CloneSpaceProject.ps1 script it will detect that you have specified that step and will make sure all the child projects are included in the Projects to Clone List. For example, if you sent in Deploy a Release as the project name, which deployed Hello World, it will set the projects to clone param for CloneSpace.ps1 to be Hello world,Deploy a release. It will also go through the hello world project and reconcile any required dependencies.

In addition, added some better logging as to why a logo gets cloned or skipped.

Clone Step Template Logo Parameter

This release adds the Clone Step Template Logo parameter allowing you skip over step template logos.

This release also fixes the following issues:

• #32 - Trailing and leading spaces in filters are now trimmed out so a project filter of Project A, Project B is treated the same as Project A,Project B
• #33 - Any error calling the Octopus Deploy API now has the entire error message written to the console (and the log).

Minor bug fixes

This release fixes the following bugs:

• #27
• #28
• #29
• #30
• #31

Removing Defaults for ChannelsToClone and RunbooksToClone

ChannelsToClone and RunbooksToClone were newer parameters, and because of that they had a default set to all. This was causing confusion as they were the only parameters that behaved that way. Those defaults have been removed.

Library Variable Sets to Exclude / Include

This release adds the following changes to the Space Cloner:

• Added LibraryVariableSetsToInclude and LibraryVariableSetsToExclude to the CloneSpaceProject.ps1. Just like the other include/exclude parameters, you can only set one. If you pass null to both of them then LibraryVariableSetsToInclude will be set to all and clone all library variable sets
• Added a timer to CloneSpace.ps1 to calculate how long a clone takes.
• Updated the worker pool cloner to not skip the default worker pool clone when going from self-hosted to the cloud. What will happen now is the worker pool will be cloned, but it won't be marked as "IsDefault".
• Revamped the Get-OctopusItemById to use where-object instead of a foreach loop