From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.6 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id C2B981F463 for ; Fri, 20 Dec 2019 09:30:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727221AbfLTJaC (ORCPT ); Fri, 20 Dec 2019 04:30:02 -0500 Received: from mail-ed1-f54.google.com ([209.85.208.54]:42368 "EHLO mail-ed1-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727167AbfLTJaC (ORCPT ); Fri, 20 Dec 2019 04:30:02 -0500 Received: by mail-ed1-f54.google.com with SMTP id e10so7595349edv.9 for ; Fri, 20 Dec 2019 01:30:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=oVZmK+Y+fDm8T/au+90JOMa2pdJBE88lsjIZJ+vHgNE=; b=CQbolV+CfelasqHKeO8z83HHI/2lAZHcwX0UOO4MgM4m4TeHzCu5ls9WhxUYZ0qjXA iSV9UDN+817vmsJSGactv11PLsErMEsCwEdf1J7wtCYaHPN5lTCGF3Z7MT3pW26GP6wG cyig9a6pvpGaU+ZtQj3dReZjSXvEyn3XOXlqB9PNg+6rwoXtxNnVseN/6HOXnIdxC/Il QaiWYMAsSTgt9eK9jeX1vjGidImyb+gaqPnpCsjjd5Xb4I31FBi5CrjtSdkxve1X/PMA ta9TpRdN8NLmzFpyEFm7a/8wKkgzIzkDENv/iCUL/+OjZgioc1NyyTquF67u7QboI2zD f+mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=oVZmK+Y+fDm8T/au+90JOMa2pdJBE88lsjIZJ+vHgNE=; b=jR1u3J292mMmLieq77VwdvZn7gtbzAHQY+FocnfPPpwxUf9Mm96pHoPfV05dOIXRgW QC0L900vaGc6f0msAyarWn08TpjVMhZ4Sng936HHBI7IyZTmz/c+/IRsz7PU0a6i10+v rV6R6GGIEm1Xtz5ZJ78OwO7LdDh9K0MA1fN4lq/HyjDzBt2CRqhBUsn1Nij/FYk9vFup T2Sjbpnr/SD+QS0hNBGX88f4npk9bohZ+8ppTMm6FPqe9rWHyEVvCinEawaM3p+Filxx ot6js3/t9UZJAZqwq+L4o9/ZvocRcXSEp1kxrY04acmLRqz14XaYz6IjytN3kmX6wDJD TeOg== X-Gm-Message-State: APjAAAX6fYfq3mlM0vcwlCgRX/ogfcsMSLRZXAaX/WF1ZE/Nii2HDewz 6Au4RAGev4YYfIQG9GGA2QB462df4XTIBRiHihvyhAgi X-Google-Smtp-Source: APXvYqyblveBOvSYyrTcEJbv+GmwZsGBo2J8BY6FvQdl79E6awwGHbHOvZSyJMz2x+JmDM4+X0DnIZlvi9A1RUR91sI= X-Received: by 2002:a17:906:aec7:: with SMTP id me7mr14598862ejb.81.1576834200135; Fri, 20 Dec 2019 01:30:00 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Christian Couder Date: Fri, 20 Dec 2019 10:29:49 +0100 Message-ID: Subject: Re: IaC monitoring with Git To: =?UTF-8?Q?Christopher_D=C3=ADaz_Riveros?= Cc: Git List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Hi, On Thu, Dec 19, 2019 at 10:31 PM Christopher D=C3=ADaz Riveros 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.