Internet Explorer is no longer supported. Many things will still work, but your experience will be degraded and some things won't function. Please use a modern browser such as Edge, Chrome, or Firefox.

Issues Overview

This application is not configured to allow new issues to be created.

922.0.1closedFIX: IIS::Ensure-AppPool may overwrite Username/Password in identity
931.12.3closedFIX: IIS::Ensure-AppPool may overwrite Username/Password in identity (1.12 backport)
901.12.2closedFIX: EnusreIISAppPool does nto show the PeriodicRestartSchedule operation property
871.12.0closedUpgrade to SDK 1.12.0
831.7.3closedFIX: PowerShell operations should respect OtterScript's WorkingDirectory
761.7.1closedFix PowerShell receiving OtterScript lists as string arrays.
781.7.0closedUpdate to SDK 1.7.0
841.6.3closedFIX: PowerShell scripts fail when current working directory doesn't exist [regression]
821.6.1closedFIX: Possible unhandled exception trying to extract description for PSCall operation that references a script in a pipeline raft
811.6.0openFIX: Use correct default raft name when resolving PowerShell scripts for Otter
801.6.0closedFIX: PSCall is not resolving scripts in pipeline-rafts in Otter
701.0.17closedAllows $PsCredential function to reference UserNamePassword credentials
Currently, the function arguments are username and password, which requires `$CredentialProperty` on an existing set of credentials. The function should also be able to accept a name of an existing instance of `UserNamePasswordCredentials` and use those as well.
731.0.16closedAdd SuccessExitCode to PSExec and PSCall
This should be identical to Execute Process, except that it should default to null as to keep with current behavior. `SuccessExitCode` **Success exit code**. Integer exit code which indicates no error. The default is empty, which means that the error code will not be used to evaluate success. This can also be an integer prefixed with an inequality operator (e.g. ">=0" or "<5").
751.0.16closedFIX: IIS::Ensure-Site should only operate on the root application for multi-application sites
If there are multiple applications defined for an IIS Site, the `IIS::Ensure-Site` operation currently configures the first one based on the order defined in `applicationHost.config`. Instead, it should look for the element with `path="/"`, and configure that application. Additional IIS applications should be defined using `IIS::Ensure-Application`.