New Resources for ElasticSearch, NSSM, 7zip and JRE about dsc HOT 15 CLOSED

First that'd be awesome if you published those I was looking to play with Elastic Search and Kibana soon and that'll help stand up stuff quciker.

Secondly I'm not sure GripDevResources is a great name. What does Grip have to do with these resources? Though I'm coming up on a blank for better names.

from dsc.

Cool, yeah resources will setup a windows box with Kibana and Elasticsearch services in default config nice a quickly. Depending usage was going to look at cluster setup further down the line, very much just evaluating at the moment.

Agreed, logic goes that I blog as gripdev so followed the naming convention of other resources that are a mixed bag of stuff, like the stackoverflowresources repo.

Happy to go with whatever fits best really!

from dsc.

👍 for ELK DSC Resources

from dsc.

I am of the opinion that the resources should be named after a grouping of what they do and not necessarily after the author. It'll help the duplication of resources where people are unware that the DSC Resource they want exists if they go into a custom name (such as StackExchange). Even the PS team has done this with xService in the xPSDesiredStateConfiguration module. Which personally I find confusing to try to rememer to find.

from dsc.

It's a tough call as collectively the resources allow the install of Elasticsearch and Kibana but I plan to reuse the JRE stuff, cNSSM and c7zip modules to create a DSC for SonarQube.

In that scenario I'd have a cElastic and cSonarQube repo with duplicated resources which doesn't feel nice.

from dsc.

While it may not ideal you could create c7zip and cNSSM as their own DSC resources and reference them in cElastic and cSonarQube as composite resources allowing the c7zip and cNSSM to be their own resources and projects for people to reference in their own resources.

from dsc.

Sounds like a good plan, shall we go for cElastic then?

from dsc.

Sounds good to me. I'll gladly give you feedback and run some tests if you want. Just let me know!

from dsc.

Thanks, it's fairly rough and ready so could do with some feedback and contributions.

@smurawski or @dlwyatt can you create a repo for the resources in the org?

from dsc.

I've created a repo, but let's stop with the 'c' stuff.

from dsc.

@smurawski Thanks for setting up the repo, tried to push but doesn't look the GripDevResources Team has access to it.

from dsc.

Sorry, will check that in a few.

from dsc.

@lawrencegripper Should be fixed now.

from dsc.

Thanks, all sorted resources pushed now

What's the move away from the c prefix about, happy to refactor? Was following the convention around c for Community and x for Experimental from MS blog post I read a while back.

from dsc.

'c' was for resources forked from microsoft's 'x' resources. Now those resources are finally on Github and we can start the process of pushing our changes upstream and hopefully deprecating any 'c' resources.

from dsc.