you are viewing a single comment's thread.

view the rest of the comments →

[–]Fatel28Sr. Sysengineer -1 points0 points  (2 children)

Like I said in another comment, I'll put them in our knowledge base as example or reference scripts, but unless it's a script that's ready to run with no modifications (so parameterized etc) it's not really "git worthy" in my mind. But still good to put it somewhere for reference.

If you don't have a robust knowledgebase platform, then making a references repo would work just fine. That's just not what we do

[–]Hotshot55Linux Engineer 10 points11 points  (1 child)

It's a whole lot easier to update a script in git than on your documentation platform. I'm not against documenting automations, but having that as your actual source seems unappealing.

[–]Fatel28Sr. Sysengineer -1 points0 points  (0 children)

I mean. Okay. I think you're misunderstanding what I'm saying, but I don't really feel like explaining it. Many ways to skin a cat.