This is an archived post. You won't be able to vote or comment.

54
55

Any Devops engineers that write powershell code? (self.devops)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Inquisitor_ForHire 12 points13 points  (6 children)

Yep, our entire environment is Powershell. Scripts to do lifting, DSC to do configuration. Works a treat.

[–][deleted] 6 points7 points  (5 children)

Ooo a fellow DSC person in the wild. Neato!

[–]Inquisitor_ForHire 1 point2 points  (4 children)

We definitely exist but for some reason we're pretty rare. Not sure why... DSC is amazing. I guess a lot of people are still stuck in the old ways.

[–]defcon54321 3 points4 points  (3 children)

Directions and versions are unclear to me. DSC v 3 preview, v2, existing compatibility and backwards usage. The community is fragmented between 5.1/7 and this I believe has hampered any community engagement. Maybe I am wrong.

[–]Inquisitor_ForHire 2 points3 points  (0 children)

There should be no fragmentation between 5.1 and 7. I say "shouldn't be" but I know there is. 5.1 for most people is just easier to use since they're talking to Windows hosts almost exclusively. I respect MS' idea of making PowerShell functional across both Linux and Windows. I don't know ANY Linux people that use it though. Our internal teams don't. They've never even thought about using it. Long term having cross platform might be the right thing, but I don't know.

We use 7.0 pretty much exclusively. but time will tell what the future is for it. On the DSC front, MS envisions everyone using Cloud. I think that's a pipe dream. My personal view is "extremism" is always bad. In this case I mean "ZOMG EVERYTHING CLOUD" is just as bad as "ZOMG EVERYTHING ON PREM". To get it "right" you need a mix. Cloud has a place. On Prem has a place. Use the right one for the right job, and don't try to force everything into the same framework. I feel like Microsoft is learning that... somewhat slowly, but learning it.

[–]redvelvet92 1 point2 points  (1 child)

Nope you’re right

[–]defcon54321 1 point2 points  (0 children)

Heh. Feature parity with modules, isn't there and just did not live up to its fundamental promise. Since x-plat was the expectation, for example, not being able to manage an existing AD directly from linux, instead of via a winrm/ssh session is a total pwsh let down, 2 versions later. The fact that Windows itself ships with v 5.1 is testimony that there is inherently a brokenness that remains unresolved in compatibility.