@gdivis

@rhessinger Thanks a lot. I will try it.

@atripp Thank you Just one small quesiton: When do you plan to make the UPack raft available for both BuildMaster and Otter ?

@rhessinger Good news thank you

thanks!! Very interesting to see.

Hello; For this, we recommend just doing a Backup and Restore. Of course, the Detatch/Reattach is effectively the same thing, but don't forget the config. For the Git-based raft, the Database just contains the connection information to the Bitbucket repository... so it will just come over with the database.

Alright, fair enough. As I use Otter almost exclusively for checking for compliance, I will look forward to this. Nontrivial asks are always the best ones, right? :D

I'll see if we can get a new version built that includes an option to output the full log to the console after a job completes. In the meantime, you could call romp with a simple batch script like: romp install %1 romp jobs logs Then invoke it with: romp.bat <packageName> Let me know if that's helpful!

Hi Philippe, Thank you for the report, this has been fixed internally and will be released in the next maintenance release on Dec. 6. The associated issue is here: https://inedo.myjetbrains.com/youtrack/issue/OT-360 Thanks, -John

We definitely want to add these as first-class Operations in our Windows extensions, but in the mean time the best route is to use the PSDsc Operation to invoke the Windows Feature DSC Resource PSDSC WindowsFeature ( Name: Web-Server, Ensure: present ); Hope that helps!

We recently moved our documentation; do you know where you found those 404s? We're also monitoring via Analytics Tools as well, but finding sooner is better :) Anyways PSCall is good in Orchestration Plans (can be done in a Configuration Plan, under some conditions), and PSEnsure is best for Configuration Plans. Explaining Ensure vs Execute can be tricky, but I'd recommend checking out our ebook, called Windows-first Guide to Infrastructure as Code and Continuous Configuration Automation :)

Thanks for tracking those down, I updated owner on them :)

We hope to include this ability in a future release, but it's a bit more complicated to get the details worked out. For now, just uninstall, then reinstall (pick version you want) will work.

Thanks Philipe; all operation documentation is automatically updated within the software once the latest version of the relevant extension is installed (i.e. the Windows extension in this case). The documentation on the website will also get updated with any minor version of the software is released, or the Inedo.SDK is updated. Hope this helps, -Tod

So I looked over OT-331, and while close, I am looking for each role to report the status of each server that has that role assigned to it, and whether it has drifted or is current. Thanks!

Alright, I have my one token agent I had to update. Thanks!

hi Jonathan, can you help me with a test case on the duplicate server issue? Are you trying do an infrastructure import that has the same server name defined twice in the same JSON document?

This can occur if the username/password credentials for Git are invalid, or more commonly, if a Git raft is configured as read-only (which probably doesn't require authentication e.g. GitHub) then is reconfigured to support write operations.

There haven't been any other feature requests for this, and we haven't researched the feasibility of doing it; however we did add Impersonation and Process Isolation, both which were in-demand features.

This appears to be a bug with the ProxyRequest property, i.e. if it's true (the default), the response variable is not set. The tracking issue for this is here: https://github.com/Inedo/inedox-inedocore/issues/91