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

Re: IaC monitoring with Git

From
Christian Couder <christian.couder@gmail.com>
Date
Dec 20, 2019, 09:29 UTC
Message-ID
<CAP8UFD231wb124-fKQcv-ddG96xncHanOnZA4jWEU3-shxTkGw@mail.gmail.com>
In-Reply-To
<CAHCo6soNwee3hN4i6v0KtxphKHa96v--e41KRqfHKV5i45OqcA@mail.gmail.com>
Hi,

On Thu, Dec 19, 2019 at 10:31 PM Christopher Díaz Riveros <christopher.diaz.riv@gmail.com> wrote:

> 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?

You might find it easier and simpler to use CI tools like Travis CI, Circle CI, GitLab pipelines, GitHub Actions, and so on to run the checks instead of using a hook.

Show 5 quoted lines
> 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)?
Many CI tools let you schedule jobs regularly.

Best, Christian.

Previous: Christopher Díaz Riveros
Message 2 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.