ramblingcookiemonster / dots Goto Github PK

Existing docs aren't particularly useful. Include a doc that shows how to do this in an internal repo...

• With Ci/CD to publish dots-sourced data when appropriate
• With a Dots-runner script that includes organization specific parameters
• With data and script paths independent from the Dots module

Maybe blog. It's been a while.

This would benefit from having more out-of-box data sources...

These are done, just need some clean up prior to publishing:

• Cobbler via xmlrpc fun
• LocalGroupMemberships (via serialized output from this)
• MSSQL (Instances via serialized output from this, or switch to Boe's now that he pulls WMI data as well)
• Software (via serialized output from this)
• OpenNebula guest data for Server nodes via xmlrpc fun

Other ideas - will break into issues if anyone actually has a use for this, but guessing I'm on my own : )

• Foreman data for Server nodes
• Profile data represented as relationship from Server node to User node
• MSSqlDatabase nodes related back to MSSqlInstance nodes
• WMI data for Server nodes (e.g. OS, last reboot, OS install date, page file info, etc.)
• Logical disk nodes (via WMI)
• Network adapter nodes (via WMI)
• Hyper-V guest data for Server nodes
• Services. i.e. win32_services

Dots scripts allow parameters, but offer no option to actually change these when calling Connect-TheDots. A jankier version allowed a .ps1 per script where variables could be defined to overwrite parameters... a slightly-less-awful method might be something like this:

Connect-TheDots -Parameters @{
    ADComputers = @{
        ExcludeOlderThanMonths = 3
    }
}

Basically:

-Parameters @{
    DotsScript1BaseName = @{
        Param1Name = Param1Value
        Param2Name = Param2Value
    }
    DotsScript2BaseName = @{
        Param1Name = Param1Value
        Param2Name = Param2Value
    }
}

Dots scripts should each include comment-based help, and their paths should be easily discoverable by the user (e.g. Get-DotsScript)

Maybe don't do this.

Configuration module might help.

Neo4j configuration might be worth storing here as well, vs. instructing folks to configure PSNeo4j

It's 2018

So uh... if anyone is interested in using Dots, already uses PuppetDB, and wants the PuppetDB ExternalSources script to work, ping me. Otherwise, cleaning this up and releasing it is on the backburner.