Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 14:27
    niwdeflorez opened #694
  • Sep 09 17:16
    birendrabisht26 opened #693
  • Sep 04 20:48
    ryanwilde opened #692
  • Aug 30 19:38
    SullySullenstein opened #691
  • Aug 30 08:14
    pshearduk commented #227
  • Aug 29 12:45
    brahmjeetsngh opened #690
  • Aug 23 12:53
    jm-73 closed #670
  • Aug 14 11:43
    aungkyawthu opened #689
  • Aug 14 10:15
    jm-73 closed #671
  • Aug 14 10:15
    jm-73 commented #671
  • Aug 14 08:27
    a13xchan opened #688
  • Aug 06 08:29
    a13xchan commented #687
  • Aug 06 08:29
    a13xchan commented #687
  • Jul 22 13:51
    jaiw23 edited #687
  • Jul 22 13:51
    jaiw23 commented #687
  • Jul 22 13:50
    jaiw23 opened #687
  • Jul 22 02:08
    JediNite reopened #686
  • Jul 22 02:07
    JediNite closed #686
  • Jul 22 02:07
    JediNite commented #686
  • Jul 22 02:07
    JediNite opened #686
Kevin Kirkpatrick
@vScripter
Alan Renouf
@alanrenouf
@vScripter i like the module idea, it was created before modules existed so thats a great thought now, easier to install in the future, i wonder how we could still make it easy to contribute to and have plugins in a module format.
@Sneddo good idea about adding @vScripter as a contributor, would you be ok with that @vScripter? That way we can always make sure we don't accept our own contributions, there is always an additional checker.
Hey I am liking this chat interface, even looks cool on the iPhone
Sneddo
@Sneddo
yeah, it's really neat! :)
Kevin Kirkpatrick
@vScripter
@alanrenouf Absolutely good with me! The notion of maintaining ease of contribution is something I have also been thinking about. That said, I really think if we can get things into modules, make sure functions have proper comment based help, add good documentation in an about_help file and have good overall documentation in the repo on how to contribute, I think it might actually be easier for people to get up to speed. We would basically be implementing PowerShell standard best practices so there would be greater continuity for people that are familiar with PowerShell but not so familiar with vCheck; the opposite of that would be people that are learning PowerShell, because they want/are using vCheck, it will help them transition leverage PowerShell for their daily workflow.
Alan Renouf
@alanrenouf
Lets do this!
Added @vScripter Welcome! I don't get to spend as much time as i like on there but @Sneddo does an awesome job! Doesn't mean I don't keep an eye on my baby, even if it has grown up!
Kevin Kirkpatrick
@vScripter
Myself and @Sneddo have also talked about getting a 'Settings' GUI form put together (more like resurrecting -> #270 )
Alan Renouf
@alanrenouf
Yeah thats been needed for a while, there is still a place for a GUI sometimes :)
Kevin Kirkpatrick
@vScripter
@alanrenouf You mean Product Managers don't get to write code all day ;)
Sneddo
@Sneddo
they have minions for that I hear
Alan Renouf
@alanrenouf
N
Very smart minions that have a lot of work to do as well :)
Sneddo
@Sneddo
that's why you have a big whip are paid the big bucks ;)
Alan Renouf
@alanrenouf
Ha ha big bucks yeah right
Sneddo
@Sneddo
we can all dream...
Alan Renouf
@alanrenouf
Maybe I should add ads to vCheck then I can retire :)
Kevin Kirkpatrick
@vScripter
Lol, just start nesting them in Write-Progress bars
Sneddo
@Sneddo
or package it with Cryptolocker :P
Sneddo
@Sneddo
actually maybe we should start a new trend of "in-script" purchases and DLC for Powershell
Kevin Kirkpatrick
@vScripter

Cleaned house and organized all open issues. Waffle board is starting to look good and makes some sense of what's outstanding. Any issues that should be reviewed as a potential feature have been tagged as enhancement and added to the 7.0 milestone.

Stories in Ready

Sneddo
@Sneddo
Awesome work!
Alan Renouf
@alanrenouf
Agreed, awesome job!
Kevin Kirkpatrick
@vScripter
:octocat: :thumbsup:
Kevin Kirkpatrick
@vScripter
I was thinking about the need for XML files for certain pieces and parts; has there been any thoughts about switching to JSON for the structured data/'schema' based portions of the report? I think it's a bit more 'readable' and PowerShell has good native support for it. Just throwing an idea out there.
Alan Renouf
@alanrenouf
Which pieces and parts? But in generally I agree JSON is the way to go, I see it being preferred to XML recently.
Kevin Kirkpatrick
@vScripter
I have no idea why I even said 'pieces & parts'; the only thing I had in my head was the Plugins.xmlfile.
Alan Renouf
@alanrenouf
:) yeah we could always convert that
Kevin Kirkpatrick
@vScripter
but it could end up scaling or being used for anything where we would need to store key-value paired data. I agree that it seems to be the internet's most popular means of storing and using structured data of all kinds. I guess it's not surprising, given the fact that IT Infrastructure is basically a sea of APIs, now (love me some APIs); I don't think I've ran across a recent API interface that doesn't take/mandate a JSON payload, lol
Alan Renouf
@alanrenouf
Tell me about it, if this were NDA I could talk about this subject all day, or maybe I already did
Kevin Kirkpatrick
@vScripter
I'm covered under current VMware NDA looks left; looks right Lol
Alan Renouf
@alanrenouf
:)
Kevin Kirkpatrick
@vScripter
In case anyone missed this earlier today, Microsoft announced/released Visual Studio Code which is a free, multi platform editor, geared toward supporting ASP.NET v5 & Node.js web applications.
It also has native support for git and syntax highlighting for PowerShell (and defaults to CRLF line endings when writing PowerShell code in OS X :smirk: )
Alan Renouf
@alanrenouf
Writing PowerShell code on OSX, if only they had open sourced Powershell as well, then maybe you could run the code on OSX as well
Kevin Kirkpatrick
@vScripter
Actually, they did!
Well, kind of..
.NET Core CLR is now available for OS X and a new Core CLR version of PowerShell is going to have to be used to manage those end points, as I understood it.
Alan Renouf
@alanrenouf
Let see what happens then, PowerShell and PowerCLI for Linux and OSX would be sweet
Kevin Kirkpatrick
@vScripter
I agree 100%
Kevin Kirkpatrick
@vScripter
@alanrenouf Do you know if it's possible to reuse/pass an authenticated PowerCLI session into a child .NET runspace, in order to be used for async' script execution?
Alan Renouf
@alanrenouf
I normally pass the
Whoops hit enter too fast, I normally pass the session secret and use that to connect to the vcenter server $session = $global:DefaultVIServer.sessionsecret
Then connect-viserver VC -session $session
If your doing this for jobs go careful, I had vCheck working with jobs but it takes a lot of resources from the client machine and kills the process.
I mean specifically for vCheck that is, not jobs in general
Kevin Kirkpatrick
@vScripter
@alanrenouf Cool; that's what I was thinking, as far as method. I thought about using it for vCheck, but I am working on a reasonably high priority request and I think seperate .NET runspaces could potentially eliminate some unnecessary overhead. That said, I'm going to keep a closer eye out on resource consumption, per your comment. Thanks a lot :thumbsup:
mtterry13
@mtterry13
Anyone available for assistance configuring this to run as scheduled task. I must be missing something, or at least right direction for debug?