From: "Christopher Díaz Riveros" <christopher.diaz.riv@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: IaC monitoring with Git
Date: Thu, 19 Dec 2019 15:30:15 -0600 [thread overview]
Message-ID: <CAHCo6soNwee3hN4i6v0KtxphKHa96v--e41KRqfHKV5i45OqcA@mail.gmail.com> (raw)
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 reply other threads:[~2019-12-19 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 21:30 Christopher Díaz Riveros [this message]
2019-12-20 9:29 ` IaC monitoring with Git Christian Couder
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=CAHCo6soNwee3hN4i6v0KtxphKHa96v--e41KRqfHKV5i45OqcA@mail.gmail.com \
--to=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).