Topics created by philippe.camelio_3885

Hi @philippe-camelio_3885 , We haven't investigated or changed this code in very many years (especially within the last year), so I wouldn't expect a changed result. Can you try the same troubleshooting steps as above? To find out where the invalid JSON is? Maybe it's comma again? FYI - we use Newtonsoft.Json for both serializing and deserializing (as you can see from error). It's really odd to be generating invalid JSON, but that's what the message is It could be related to an obscure bug, etc. We just have no idea and haven't investigated in past year. Thanks, Alana

Thanks

Good news

Thanks you Rich it is working !.

Hi @philippe-camelio_3885, This has been fixed and will be released in Otter 3.0.13 which is expected to be released on October 22nd 2021. Thanks, Dan

@rhessinger Thanks

@gdivis Thanks for the resolution

Hi @philippe-camelio_3885, I have just built a new CI version of the [Scripting Extension 1.10.3-CI.3] (https://proget.inedo.com/feeds/PrereleaseExtensions/inedox/Scripting/1.10.3-CI.3). This version includes the Minimum Version on Ensure PS Module and adds a new Ensure-PsRepository operation. Please take a look and let me know if you have any issues. Thanks, Rich

@apxltd Thank you, problem fixed

@atripp Oups Sorry about that. I made other tests since I created the thread. The data I send you are not correct I will wait for the 3.0.6 to make a clean test case and update the thread.

Thank you Alex bug is gone

@rhessinger said in Agent 49 - Otter 2 / Otter 3 ?: t you should be able to use the same agent install on more than one intance (Otter 3 and Otter 2.2) at the same time without issue. Basically, you can add that same agent to both Otter instances you have. Good news Thank you

thank you @rhessinger It is working fine. I have now to mix this version with the Scripting v1.10.2-CI.1 (bug for PSEnsure) Thank you guys for the fast correction

Thank you

@atripp said in [Otter 3] Upgrade Inedo Agent failed: m here, I recommend to just reinstall v49 on the serve Reinstall the v49 directly is working but as the config file move and its format change I have to modify my autoregistration deployment script Thanks for the reply

@stevedennis Thanks

Good idea Thanks

Hello, This is a bug, in that PSVerify shouldn't show up on the statement list. Instead, your scripts should, in a manner like this, with a Script Execution mode: Then, they'll look in Otter like this: PSVerify VerifyFreeSpace ( MinimumFreeGB: 24, DriveToVerify: C ); Here's how this script works behind the scenes... <# .DESCRIPTION Verifies that an hdars server has the required and expected configuration .AHDESIREDVALUE True .AHCURRENTVALUE $AmpleFreeSpace .PARAMETER DriveToVerify The drive letter (such as "C") for what to verify .PARAMETER MinimumFreeGB The minimum free space required on the drive, in gigabytes #> param ([int]$MinimumFreeGB = 20, [string]$DriveToVerify = "C") $ActualFreeGB = [int]((Get-PSDrive $DriveToVerify).Free / (1024 * 1024 * 1024)) $AmpleFreeSpace = $ActualFreeGB -gt $MinimumFreeGB And for reference, the additional help parameter descriptions... .AHDESIREDVALUE This is what you wish the configuration value to be. When not specified, the value of $true is assumed. .AHCURRENTVALUE This is the actual value of the configuration. When not specified, script's output is used. .AHCONFIGKEY This is the "configuration key" used by the script, which is a string that uniquely identifies configuration on a server. It's like a file on disk (a file is uniquely identified by its name), or the name of an IIS Application pool (an application pool is unqiuely identified by its name). Optional. When not specified, the name of the script is used. .AHVALUEDRIFTED This is an indicator as to whether the value is considered drifted. When not specified, it's a string comparison of the desired and current value. .AHEXECMODE This is either "Collect" or "Configure", and is only used on PSEnsure operations; it will be ignored (or set to Collect, depending on what's easier to code) on PSVerify. Using a PSEnsure without a .AHEXECMODE will cause an error. The Additional Help items can be specified as a value or a variable; variables will simply start with a $.

@philippe-camelio_3885 oh i see; you mean, capture the output of a process or script execution into a variable or something. Definitely something to consider as an enhancement, I think. That wouldnt' be too bad (though the variable could get huge, and rutnime variables raen't realy designed for large amounts of text like that)