It seems the part is causing '1' to be converted to a decimal: https://github.com/Inedo/inedox-windows/blob/88f5924bc1d2397c9edfb135eb9429bbe9fa34e8/Windows/OtterExtension/Operations/PSDscOperation.cs#L241-L243 Of course, because OtterScript is only strings, there's no way to know if it "should" be a string or a decimal. I wonder if the property could be inspected of the dsc resource? I'll note you can shorten @([string[]](1)) to @('1'),

Thanks Phillipe, we've identified the bug and will fix it in next maintence release as [OTTER-133]

It is working :) Thank you Have a nice week-end Regards Philippe

Thank you for the report. This will be resolved in the next maintenance release as issue OTTER-130.

Pb solved with the 1.5.2

Pb solved with the 1.5.2

I was able to reproduce this, it only happens when a child environment is created for first time. The case is OTTER-121, and wil be resolved in a future maintenance release.

Hi Philippe , I think i understand, but it's much easier to visualize :) Especially once we see your data. could you send a screenshot to us via support - at Inedo - dot com? And feel free to hilite the areas, etc. you suggest to improve.

Hello Thank you for the reply. I use OTTER for a few weeks now, So I have to understand the otter model :) I will apply my DSC in a classical way (start-DSCconfiguration script) Regards Philippe

The easiest option would just be to use the PowerShell Agent, which does not require any installation and simply uses remote PowerShell. However, if you can't use this or don't want to due to performance issues, you can manually install the Otter/Inedo agent by downloading the manual install package for the latest version of Otter here: http://inedo.com/otter/versions The instructions for installing the agent manually can be found here: http://inedo.com/support/documentation/otter/installation/manual

Thanks Philippe, looks like you identified the bug and workaround. It will be addressed as OTTER-119

Did you change the name of the branch after cloning? When cloned, branches should automatically track the remote branch. One option is to navigate to the local GitRafts directory in the Execution.DefaultWorkingDirectory path (found in All Settings), and delete the local workspace and try again. If you have git installed on the same server as Otter, you can manually configure the repo to track the remote branch using the commands outlined here: http://stackoverflow.com/a/2286030