From: Christian Couder <christian.couder@gmail.com>
To: "Christopher Díaz Riveros" <christopher.diaz.riv@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: IaC monitoring with Git
Date: Fri, 20 Dec 2019 10:29:49 +0100 [thread overview]
Message-ID: <CAP8UFD231wb124-fKQcv-ddG96xncHanOnZA4jWEU3-shxTkGw@mail.gmail.com> (raw)
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.
> 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.
prev parent reply other threads:[~2019-12-20 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 21:30 IaC monitoring with Git Christopher Díaz Riveros
2019-12-20 9:29 ` Christian Couder [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP8UFD231wb124-fKQcv-ddG96xncHanOnZA4jWEU3-shxTkGw@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=christopher.diaz.riv@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).