$supersecure = convertto-securestring "sdfdsfd" -asplaintext -force

New-Object System.Management.Automation.PSCredential -ArgumentList "username", (ConvertTo-SecureString "really secure" -AsPlainText -Force)

$sneaky = ctss "sneaky convert" -asplainText -force
#[SuppressMessage("Microsoft.Security", "CS002:SecretInNextLine", Justification="Test/NotASecret.")]
$supersecure = convertto-securestring "sdfdsfd" -asplaintext -force

New-Object System.Management.Automation.PSCredential -ArgumentList "username", (ConvertTo-SecureString "really secure" -AsPlainText -Force)

$sneaky = ctss "sneaky convert" -asplainText -force

Add suppression of warning for MS policy
Add suppression of warning for MS policy

Because we are using a direct invocation of ConvertTo-SecureString it triggers a warning by MS tools that secrets are not allowed to be checked in to our repository. This suppresses this warning.
