Hi Alana, Thanks for your reply. I ended up submitting a bug Ticket which I need to respond to. But in response to your comment, The Agent and the runtime user are both the same account. Aside from the simple script above, I also tried to get it to return the value, and it would only return 's' in once case, error in another , or indicate the value was part of a Dictionary, which I'm guessing is meaning its within an array. Tod Hoven is my contact for the issue that I will be working with, but at the moment my BuildMaster instance is offline, so I will be following-up once our environment is back online. I'll try and remember to update this thread with the fix once we have it... -Trent

Awesome Ben, thanks for the quick action! I've followed the issue, will I get an automated notification when it's known in which version the fix is going to be available?

Just as an update to this, we have updated the behavior of how role dependencies work to better support this scenario. Given the original example... B (Collect) D (Collect) B (Configure) D (Configure) The new behavior will be that, if "B" reports drift, then "D" (as a dependent role) will also be considered drifted, and then both B and D will be configured as expected.

Unfortunately, no, I was not. I'm in the process of taking a look at ProGet running in containers again, I will test in the near future and let you know. I don't expect it to be working unless something changed with the containers in the last several months.

Hello Tom and Brett, The endpoint being requested seems simple enough. For example, here's what it requests for -StartWith Inedo.. I've filed PG-1281 to add an implementation of this endpoint.

Can you provide a example for this not working? The Add-Member cmdlet interacts with PSObjects, but the OUt-String does interact with the host (which, is different than an output stream... and has some strange handling sometimes).

Correct. Output variables don't need to be specially declared. However, the next version of the Windows plugin for BuildMaster and Otter will add support for [ref] parameters as output variables in the editor.

Thanks. That of course fixed it.

Just a quick update... Upon researching it further, it seems that modifying PSCall in this manner might be quite a bit complicated; not so much technically, but we'd have to balance with how PSExec works as well. Definitely something for us to consider as we work towards getting closer with PowerShell/DSC in the coming versions. The current thought is to add a new variatic variable function: PSEvalAsset(OptionalRaftName::AssetName[, arg.1..n]) This could return a scalar ($), vector (@), or map (@). Unfortunately there are no named arguments in OtterScript variable functions (unlike operations), but I think that's OK... hopefully assets will be very simple and not have a lot of arguments.

There was a regression for the PowerShell agents that caused this to behave like this in some cases, but it was fixed in Otter 2.2.5 (released today). I should be fixed Let me know if this resolves your issue!

Awesome Dean. Thanks for taking a look.

ah yes, sorry. I setup the creds a couple of months ago and forgot about that option. thanks.

I was finally able to reproduce this - I had been using v5.5.0 of the Windows extension which does not exhibit this behavior. We will have a fix for either the Windows extension, BuildMaster or both shortly.

https://github.com/PowerShell/PowerShellGet/issues/76

Thanks. That was the problem. After updating the Windows extension from 5.5.0 to 5.6.0 the powershell command is working again.

BuildMaster runs the PowerShell scripts in-process, so it's not possible. The method you've identified (running a separat eprocess) is the best way to accomplish it I think.

This was a regression in 5.5.2, but will be fixed in 5.5.3 (shipping later today) As a work-around, you can use text-mode to invoke PSCall

Well i finally was able to publish to our Powershell feed. I updated the PackageManagement and PowerShellGet modules to version 1.1.0.0. which were released a few days ago... 12 Oct 2016 I hope this helps .

Please ignore this question. It works now.

Ah yes, that solved my problem. Thanks!