Merge pull request #9 from madeiramadeirabr/github_workflows

adicao de arquivo para pylint

Author: andersoncontreira

.github/workflows/pylint.yml

@@ -0,0 +1,39 @@
+# Summary:
+# Execute the pylint analysis on code
+# Read here for mode info: https://pylint.pycqa.org/en/latest/ and  https://www.python.org/dev/peps/pep-0008/
+
+name: Execute the pylint analysis
+
+#on:
+#  # There are several ways to trigger Github actions - See https://help.github.com/en/actions/reference/events-that-trigger-workflows#example-using-a-single-event for a comprehensive list:
+#  # - "push": Triggers each time a commit is pushed
+#  # - "pull_request": Triggers each time a commit is pushed within a pull request, it makes it much easier to write comments within the PR, but it suffers some strong limitations:
+#  #   - There is no way to trigger when a PR is merged into another - See https://github.community/t/pull-request-action-does-not-run-on-merge/16092?u=vadorequest
+#  #   - It won't trigger when the PR is conflicting with its base branch - See https://github.community/t/run-actions-on-pull-requests-with-merge-conflicts/17104/2?u=vadorequest
+#  push: # Triggers on each pushed commit
+#    branches:
+#      - 'master'
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        # python-version: [ '3.x', 'pypy-3.7', 'pypy-3.8' ]
+        python-version: ["3.8", "3.9", "3.10"]
+    name: Python ${{ matrix.python-version }} sample
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+          architecture: x64
+          cache: 'pip'
+      - name: Install dependencies
+      - run: |
+          python -m pip install --upgrade pip
+          pip install pylint
+      - name: Analysing the code with pylint
+      - run: pylint app.py lambda_app tests

examples/lambda_api/.github/workflows/pylint.yml

@@ -0,0 +1,39 @@
+# Summary:
+# Execute the pylint analysis on code
+# Read here for mode info: https://pylint.pycqa.org/en/latest/ and  https://www.python.org/dev/peps/pep-0008/
+
+name: Execute the pylint analysis
+
+#on:
+#  # There are several ways to trigger Github actions - See https://help.github.com/en/actions/reference/events-that-trigger-workflows#example-using-a-single-event for a comprehensive list:
+#  # - "push": Triggers each time a commit is pushed
+#  # - "pull_request": Triggers each time a commit is pushed within a pull request, it makes it much easier to write comments within the PR, but it suffers some strong limitations:
+#  #   - There is no way to trigger when a PR is merged into another - See https://github.community/t/pull-request-action-does-not-run-on-merge/16092?u=vadorequest
+#  #   - It won't trigger when the PR is conflicting with its base branch - See https://github.community/t/run-actions-on-pull-requests-with-merge-conflicts/17104/2?u=vadorequest
+#  push: # Triggers on each pushed commit
+#    branches:
+#      - 'master'
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        # python-version: [ '3.x', 'pypy-3.7', 'pypy-3.8' ]
+        python-version: ["3.8", "3.9", "3.10"]
+    name: Python ${{ matrix.python-version }} sample
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+          architecture: x64
+          cache: 'pip'
+      - name: Install dependencies
+      - run: |
+          python -m pip install --upgrade pip
+          pip install pylint
+      - name: Analysing the code with pylint
+      - run: pylint app.py lambda_app tests

examples/lambda_api/README.md

@@ -32,11 +32,41 @@ Service routes map.
 * Redis
 * Swagger
 
+## Details about requirements files
+### requirements.txt
+Collection of common application modules, light modules.
+
+### requirements.txt
+Collection of specific application modules, heavy modules that can be converted to layers if necessary.
+
+### requirements-tests.txt
+Collection of specific test application modules.
+
 ## Kong configuration
 Configure Kong API Gateway to work compatible with API Gateway.
 
 
 ## Installation
+### Installing AWS CLI
+Documentation:
+https://docs.aws.amazon.com/pt_br/cli/latest/userguide/install-cliv2.html
+
+Execute the follow command:
+```
+apt install awscli
+apt install zip
+app install pip
+```
+Execute the follow command:
+```
+aws configure
+```
+
+### Installing python venv support
+Execute the follow command:
+```
+apt install python38-env
+```
 
 ### Running Locally
 To create the `venv` and install the modules execute:

examples/lambda_api/requirements-vendor.txt

@@ -1 +1,2 @@
-boto3
+boto3
+pymysql

examples/lambda_api/requirements.txt

@@ -8,4 +8,4 @@ Flask
 pyyaml
 apispec
 marshmallow
-pymysql
+pylint

examples/lambda_sqs/.github/workflows/pylint.yml

@@ -0,0 +1,39 @@
+# Summary:
+# Execute the pylint analysis on code
+# Read here for mode info: https://pylint.pycqa.org/en/latest/ and  https://www.python.org/dev/peps/pep-0008/
+
+name: Execute the pylint analysis
+
+#on:
+#  # There are several ways to trigger Github actions - See https://help.github.com/en/actions/reference/events-that-trigger-workflows#example-using-a-single-event for a comprehensive list:
+#  # - "push": Triggers each time a commit is pushed
+#  # - "pull_request": Triggers each time a commit is pushed within a pull request, it makes it much easier to write comments within the PR, but it suffers some strong limitations:
+#  #   - There is no way to trigger when a PR is merged into another - See https://github.community/t/pull-request-action-does-not-run-on-merge/16092?u=vadorequest
+#  #   - It won't trigger when the PR is conflicting with its base branch - See https://github.community/t/run-actions-on-pull-requests-with-merge-conflicts/17104/2?u=vadorequest
+#  push: # Triggers on each pushed commit
+#    branches:
+#      - 'master'
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        # python-version: [ '3.x', 'pypy-3.7', 'pypy-3.8' ]
+        python-version: ["3.8", "3.9", "3.10"]
+    name: Python ${{ matrix.python-version }} sample
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Python
+        uses: actions/setup-python@v2
+        with:
+          python-version: ${{ matrix.python-version }}
+          architecture: x64
+          cache: 'pip'
+      - name: Install dependencies
+      - run: |
+          python -m pip install --upgrade pip
+          pip install pylint
+      - name: Analysing the code with pylint
+      - run: pylint app.py lambda_app tests

examples/lambda_sqs/README.md

@@ -30,6 +30,17 @@ There are no routes for this project.
 * MySQL
 * Redis
 
+## Details about requirements files
+### requirements.txt
+Collection of common application modules, light modules.
+
+### requirements.txt
+Collection of specific application modules, heavy modules that can be converted to layers if necessary.
+
+### requirements-tests.txt
+Collection of specific test application modules.
+
+
 ## Installation
 
 ### Installing AWS CLI
@@ -46,6 +57,11 @@ Execute the follow command:
 ```
 aws configure
 ```
+### Installing python venv support
+Execute the follow command:
+```
+apt install python38-env
+```
 
 ### Creating network
 Execute the follow command:

examples/lambda_sqs/requirements.txt

@@ -7,4 +7,5 @@ flask-cors
 Flask
 pyyaml
 apispec
-marshmallow
+marshmallow
+pylint