chore: remove serverless and terraform backends (#89)

* chore: remove serverless and terraform backends

* fix: update ci container image

* fix(ci): install jq

* fix(ci): add default shell

* docs(deploy): update docs to remove extra backends

* test(integration): adjust for flakiness

* fix(ci): missing silence in make command

* fix(integration): increase max retries

* test(ci): run the tests in pl-waw

* test(integrations): use current version when vendoring in tests

* test(ci): remove clean up

* fix: use scaleway runtime when vendoring deps

* test(integration): upgrade to python311 runtime

* fix: revert use runtime version when packaging

* fix(integration): go back to using boto3 to get gateway key

* refactor: rename upload timeout variable

* refactor: remove gateway auth key in tests.constants

Author: cyclimse

.github/actions/setup-poetry/action.yml

@@ -19,7 +19,7 @@ runs:
     - name: Install poetry dependencies
       shell: bash
       run: poetry install --no-interaction --no-root --with=dev
-      if: steps.cache-deps.outputs.cache-hit != 'true'
+      if: steps.cache-poetry-deps.outputs.cache-hit != 'true'
 
     - name: Install scw_serverless
       shell: bash

.github/actions/setup-serverless-framework/action.yml

@@ -15,9 +15,14 @@ env:
   S3_ENDPOINT: "https://s3.fr-par.scw.cloud"
   S3_REGION: "fr-par"
 
+defaults:
+  run:
+    shell: bash
+
 jobs:
   test-deployed-gateway:
-    runs-on: ubuntu-latest
+    runs-on: self-hosted
+    container: python:3.11-bullseye
     steps:
       - uses: actions/checkout@v3
 
@@ -38,6 +43,9 @@ jobs:
           default-organization-id: ${{ secrets.SCW_DEFAULT_ORGANIZATION_ID }}
           save-config: true
 
+      - name: Install jq
+        run: apt-get update && apt-get install -y jq
+
       - name: Create Gateway namespace
         working-directory: ${{ env.GATEWAY_CHECKOUT_DIR }}
         run: |

.github/workflows/integration-gateway.yml

@@ -13,17 +13,10 @@ permissions:
 jobs:
   test:
     runs-on: self-hosted
-    container: nikolaik/python-nodejs:python3.10-nodejs18
+    container: python:3.11-bullseye
     steps:
       - uses: actions/checkout@v3
 
-      - name: Install terraform
-        uses: hashicorp/setup-terraform@v2
-        with:
-          terraform_wrapper: false
-
-      - uses: ./.github/actions/setup-serverless-framework
-
       - uses: ./.github/actions/setup-poetry
 
       - name: Test with pytest

.github/workflows/pytest-integration.yml

@@ -14,7 +14,7 @@ permissions:
 jobs:
   test:
     runs-on: self-hosted
-    container: nikolaik/python-nodejs:python3.10-nodejs18
+    container: python:3.11-bullseye
     steps:
       - uses: actions/checkout@v3
 

.github/workflows/pytest.yml

@@ -11,7 +11,7 @@ permissions:
 jobs:
   deploy:
     runs-on: self-hosted
-    container: nikolaik/python-nodejs:python3.10-nodejs18
+    container: python:3.11-slim-bullseye
     steps:
       - uses: actions/checkout@v3
 

.github/workflows/python-publish.yml

@@ -69,4 +69,4 @@ If do not want your function to be publicly available, set the privacy to `priva
    def handler(event, context):
       ...
 
-.. autofunction:: scw_serverless.app.Serverless.schedule
+.. autoclass:: scw_serverless.config.triggers.CronTrigger

docs/source/configuring.rst

@@ -14,27 +14,8 @@ The `deploy` command will deploy your functions directly.
 
 The command will wait until all functions are deployed and ready to be called. It will also deploy the corresponding triggers.
 
-Generate
---------
-
-Generators will generate configuration files to use with other deployment tools.
-Currently, you can generate either a `serverless` or `terraform` configuration file. This can be useful to integrate with your existing tooling.
-
-Config file generation is done with the `generate` command:
-
-.. code-block:: console
-
-    scw-serverless generate -t serverless
-
-Serverless Generator
-^^^^^^^^^^^^^^^^^^^^
-
-.. autoclass:: scw_serverless.config.generators.ServerlessFrameworkGenerator
-
-Terraform Generator
-^^^^^^^^^^^^^^^^^^^
-
-.. autoclass:: scw_serverless.config.generators.TerraformGenerator
+If you have routed functions, the deploy command will also call your Serverless Gateway to update the routes to your function.
+For more information on the Gateway integration, see also :doc:`gateway`.
 
 Dependencies
 ------------