New-OctopusKubernetesTarget does not validate that only one authentication mechanism has been provided

[shaun-od]

Team

• I've assigned a team label to this issue

Severity

0

Version

Earliest tried 2022.3.1032 but would be in earlier versions

Latest Version

I could reproduce the problem in the latest build

What happened?

When both -octopusAccountIdOrName and -octopusClientCertificateIdOrName parameters are provided no error is thrown and certificate authentication is picked.

Reproduction

1. Add a script steps that has a powershell scripts that calls the New-OctopusKubernetesTarget command and provides both the -octopusAccountIdOrName and -octopusClientCertificateIdOrName parameters.
2. The Deployment target that is created will be using certificate authentication.

Error and Stacktrace

No response

More Information

No response

Workaround

Only provide a single parameter of either -octopusAccountIdOrName or -octopusClientCertificateIdOrName

[octoreleasebot]

Release Note: New-OctopusKubernetesTarget command will now validate that only one of the following parameters have been provided -octopusAccountIdOrName and -octopusClientCertificateIdOrName

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2022.3	2022.3.1270
2022.4+	all releases