git/list[1] front-page[2] threads[3] people[4] search[5] about
 

IaC monitoring with Git

From
Christopher Díaz Riveros <christopher.diaz.riv@gmail.com>
Date
Dec 19, 2019, 21:30 UTC
Message-ID
<CAHCo6soNwee3hN4i6v0KtxphKHa96v--e41KRqfHKV5i45OqcA@mail.gmail.com>
Hi all,

I'm trying to figure out a git based solution for a use case we have at my work place. We use IaC for our infrastructure, when we want to create new instances/accounts/etc we add a certain set of tags in our files to indicate some key aspects of the instances/accounts.

There is one specific tag, owner, which we use to set a contact point in case we need someone to make a change. The main issue with this is that you can set the tag to anything, valid or not, or it could become invalid over time.

Would a valid approach for first issue be to set a pre-receive hook in our repositories so that before the PR is merged, we check validity of the contact email, a.k.a. owner tag (we assume validity means that email exist), maybe via ldapsearch or another command like this?

For the second case, I'd assume git does not by default monitor contents of files on a regular basis, does anybody have faced this issue and successfully found a way to periodically check contents and trigger alerts on repositories based on same case (email becomes invalid, then trigger alert)?

Thanks a lot for your help!
Next: Christian Couder
Message 1 of 2 in “IaC monitoring with Git”
  1. Christopher Díaz RiverosDec 19, 2019
  2. Christian CouderDec 20, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.