[COMMON] Add and run pre-commit linters via tox

- create a .pre-commit-config.yaml configuration file with
  * gitlint
  * trailing blanks linter
  * tabs removal linter
    - exclude .git folder from it
    - exclude Makefiles since tabs are mandatory by default in them
- create a tox pre-commit profile to run it from tox
  note gitlint is not runnable at this pre-commit stage
- create pre-commit-install and pre-commit-uninstall tox profiles to
  (un)install hooks locally and (un)perform tests at each "git commit"
  call (i.e. without calling manually the pre-commit tox profile)
- precise pre-commit stages/types in the pre-commit configuration file
  so that hooks are installed correctly. This avoids messages about
  skipped tests when they are run at a wrong stage.

Issue-ID: OOM-2643
Signed-off-by: guillaume.lambert <guillaume.lambert@orange.com>
Change-Id: Ie95bb4f6f90be80b05a1398973caffeff7936881

1 files changed, 20 insertions, 20 deletions

diff --git a/kubernetes/vid/resources/config/log/vid/logback.xml b/kubernetes/vid/resources/config/log/vid/logback.xml
index 018cca8a43..17af1c990f 100644
--- a/kubernetes/vid/resources/config/log/vid/logback.xml
+++ b/kubernetes/vid/resources/config/log/vid/logback.xml
@@ -8,9 +8,9 @@
   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at
-  
+
        http://www.apache.org/licenses/LICENSE-2.0
-  
+
   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
@@ -95,11 +95,11 @@
    </appender>
 
    <!-- EELF Security Appender. This appender is used to record security events
-    to the security log file. Security events are separate from other loggers 
-    in EELF so that security log records can be captured and managed in a secure 
-    way separate from the other logs. This appender is set to never discard any 
+    to the security log file. Security events are separate from other loggers
+    in EELF so that security log records can be captured and managed in a secure
+    way separate from the other logs. This appender is set to never discard any
     events. -->
-   <!--     
+   <!--
   <appender name="EELFSecurity"
     class="ch.qos.logback.core.rolling.RollingFileAppender">
     <file>${logDirectory}/${securityLogName}.log</file>
@@ -118,14 +118,14 @@
       <pattern>${defaultPattern}</pattern>
     </encoder>
   </appender>
-  
+
   <appender name="asyncEELFSecurity" class="ch.qos.logback.classic.AsyncAppender">
     <queueSize>256</queueSize>
     <discardingThreshold>0</discardingThreshold>
     <appender-ref ref="EELFSecurity" />
   </appender>
    -->
-   <!-- EELF Performance Appender. This appender is used to record performance 
+   <!-- EELF Performance Appender. This appender is used to record performance
     records. -->
    <!--
   <appender name="EELFPerformance"
@@ -152,10 +152,10 @@
     <appender-ref ref="EELFPerformance" />
   </appender>
   -->
-   <!-- EELF Server Appender. This appender is used to record Server related 
-    logging events. The Server logger and appender are specializations of the 
-    EELF application root logger and appender. This can be used to segregate Server 
-    events from other components, or it can be eliminated to record these events 
+   <!-- EELF Server Appender. This appender is used to record Server related
+    logging events. The Server logger and appender are specializations of the
+    EELF application root logger and appender. This can be used to segregate Server
+    events from other components, or it can be eliminated to record these events
     as part of the application root log. -->
    <!--
   <appender name="EELFServer"
@@ -181,10 +181,10 @@
     <appender-ref ref="EELFServer" />
   </appender>
    -->
-   <!-- EELF Policy Appender. This appender is used to record Policy engine 
-    related logging events. The Policy logger and appender are specializations 
-    of the EELF application root logger and appender. This can be used to segregate 
-    Policy engine events from other components, or it can be eliminated to record 
+   <!-- EELF Policy Appender. This appender is used to record Policy engine
+    related logging events. The Policy logger and appender are specializations
+    of the EELF application root logger and appender. This can be used to segregate
+    Policy engine events from other components, or it can be eliminated to record
     these events as part of the application root log. -->
    <!--
   <appender name="EELFPolicy"
@@ -210,10 +210,10 @@
     <appender-ref ref="EELFPolicy" />
   </appender>
   -->
-   <!-- EELF Audit Appender. This appender is used to record audit engine 
-    related logging events. The audit logger and appender are specializations 
-    of the EELF application root logger and appender. This can be used to segregate 
-    Policy engine events from other components, or it can be eliminated to record 
+   <!-- EELF Audit Appender. This appender is used to record audit engine
+    related logging events. The audit logger and appender are specializations
+    of the EELF application root logger and appender. This can be used to segregate
+    Policy engine events from other components, or it can be eliminated to record
     these events as part of the application root log. -->
    <appender name="EELFAudit" class="ch.qos.logback.core.rolling.RollingFileAppender">
       <file>${logDirectory}/${auditLogName}.log</file>