fix: fix dependency issue, add google cloud function support

.github/workflows/coverage.yml

@@ -1,4 +1,4 @@
-name: Running Code Coverage
+name: Code coverage
 
 on: [push, pull_request]
 

.github/workflows/create-release.yml

@@ -5,8 +5,6 @@ name: Create release
 on:
   push:
     branches: [ main ]
-  pull_request:
-    branches: [ main ]
 
 jobs:
   create-release:

README.md

@@ -20,20 +20,20 @@ Inspired by [kingsoftgames/certbot-lambda](https://github.com/kingsoftgames/cert
 
 ## Deployment
 
-### AWS Lambda
-
 Download latest version of `certbot-lambda.zip` from [releases](https://github.com/KiraLT/certbot-lambda/releases).
 
-1. Create new lambda in AWS Dashboard with `Python 3.9` runtime.
-1. Upload `certbot-lambda.zip` at `Code` > `Code source` > `Upload from` > `.zip file`.
-1. Update handler to `lambdex_handler.handler` at `Code` > `Runtime settings` > `Handler`.
-1. Create new `Execution role` at `Configuration` > `Execution role` > `Edit` > `Create a new role from AWS policy templates` with name `lambda-certbot`.
-1. Go to created role by clicking on the name and `Attach policies`:
+### AWS Lambda
+
+1. Create new lambda in Google Dashboard with `Python 3.9` runtime.
+2. Upload `certbot-lambda.zip` at `Code` > `Code source` > `Upload from` > `.zip file`.
+3. Update handler to `main.handler` at `Code` > `Runtime settings` > `Handler`.
+4. Create new `Execution role` at `Configuration` > `Execution role` > `Edit` > `Create a new role from AWS policy templates` with name `lambda-certbot`.
+5. Go to created role by clicking on the name and `Attach policies`:
     * `SecretsManagerReadWrite`
     * `AmazonRoute53FullAccess`
-1. Increase execution timeout in `Configuration` > `General configuration` to 10 minutes and memory limit to 150Mb.
-1. Add ENV variables at `Configuration` > `Environment variables` (check bellow for required ENV variables).
-1. Run lambda manually one time to create a secret by going to `Test` and executing `hello-wold` template.
+6. Increase execution timeout in `Configuration` > `General configuration` to 10 minutes and memory limit to 150Mb.
+7. Add ENV variables at `Configuration` > `Environment variables` (check bellow for required ENV variables).
+8. Run lambda manually one time to create a secret by going to `Test` and executing `hello-wold` template.
 
 #### Automatic rotation
 
@@ -47,6 +47,16 @@ For that to work, update lambda and add new `Resource-based policy` at `Configur
 
 Then go to AWS Secrets dashboard and create a rotation rule for created secrets - it should execute created lambda.
 
+### Google Function
+
+1. Create new function in [Google Cloud dashboard](https://console.cloud.google.com/functions).
+2. Set trigger `Cloud Pub/Sub` _(create new topic)_.
+4. Add runtime environment variables according your needs _(check configuration section and examples bellow)_.
+5. Increase timeout to `540` seconds.
+6. Select `Python 3.9` runtime.
+7. Select `Zip upload` source code type and upload `certbot-lambda.zip` _(you may need to create storage bucket where zip will be stored)_.
+8. Deploy function.
+
 ## Environment variables
 
 | Name | Description | Default/required |
@@ -87,7 +97,7 @@ CERTBOT_DOMAINS=*.example.com,example.com
 CERTBOT_DNS_PLUGIN=dns-route53
 ```
 
-| In the [lambda](https://aws.amazon.com/lambda/) aws credentials are provided by default. Make sure lambda role has access to AWS Secrets and Route 53. Or you can [configure them manually](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html).
+> In the [lambda](https://aws.amazon.com/lambda/) aws credentials are provided by default. Make sure lambda role has access to AWS Secrets and Route 53. Or you can [configure them manually](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html).
 
 ### AWS Lambda to AWS Secrets using Cloudflare
 
@@ -100,4 +110,4 @@ CERTBOT_DNS_PLUGIN=dns-cloudflare
 CERTBOT_CREDENTIALS="dns_cloudflare_api_token = 0123456789abcdef0123456789abcdef01234567"
 ```
 
-| In the [lambda](https://aws.amazon.com/lambda/) aws credentials are provided by default. Make sure lambda role has access to AWS Secrets. Or you can [configure them manually](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html).
+> In the [lambda](https://aws.amazon.com/lambda/) aws credentials are provided by default. Make sure lambda role has access to AWS Secrets. Or you can [configure them manually](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html).

pyproject.toml

@@ -27,7 +27,6 @@ certbot-dns-rfc2136 = "^1.29.0"
 certbot-dns-sakuracloud = "^1.29.0"
 python-dotenv = "^0.20.0"
 python-slugify = "^6.1.2"
-black = "^22.6.0"
 
 [tool.poetry.dev-dependencies]
 taskipy = "^1.10.2"
@@ -36,6 +35,7 @@ lambdex = "^0.1.6"
 python-semantic-release = "^7.31.2"
 pytest = "^7.1.2"
 pytest-cov = "^3.0.0"
+black = "^22.6.0"
 
 [build-system]
 requires = ["poetry-core>=1.0.0"]
@@ -44,7 +44,7 @@ build-backend = "poetry.core.masonry.api"
 [tool.taskipy.tasks]
 build = "rm -rf ./dist && task build-pex && task build-lambda"
 build-pex = "pex . -o dist/certbot-lambda.zip"
-build-lambda = "lambdex build -e app.handler:handler dist/certbot-lambda.zip"
+build-lambda = "lambdex build -e app.handler:handler -M main.py dist/certbot-lambda.zip"
 test = "pytest --cov=app --cov-report xml tests/"
 dev = "python -c 'from app.handler import handler; handler(None, None)'"
 prettify = "black ./app ./tests"