Merge branch 'feature/e2e-tests' of github.com:mploski/aws-lambda-powertools-python into feature/e2e-tests

Author: Michal Ploski

.vscode/launch.json

@@ -0,0 +1,15 @@
+{
+    "configurations": [
+        {
+            "name": "Python: Current File",
+            "type": "python",
+            "request": "launch",
+            "program": "${file}",
+            "console": "integratedTerminal",
+            "justMyCode": true,
+            "env": {
+                "AWS_PROFILE": "aws-mploski-root"
+            }
+        }
+    ]
+}

MAINTAINERS.md

@@ -166,12 +166,13 @@ When necessary, be upfront that the time to review, approve, and implement a RFC
 
 Some examples using our initial and new RFC templates: #92, #94, #95, #991, #1226
 
-### Run end to end tests on merges to Develop branch
+### Run end to end tests
 
 In order to run end to end tests you need to install CDK CLI first and bootstrap your account with `cdk bootstrap` command. For additional details follow [documentation](https://docs.aws.amazon.com/cdk/v2/guide/bootstrapping.html).
 
-You can run tests either from your local machine's shell by exporting `AWS_PROFILE` environment variable and running `make e2e tests`. 
-You may also do this directly from GitHub Console. Run the [run-e2e-tests workflow](https://github.com/awslabs/aws-lambda-powertools-python/actions/workflows/run-e2e-tests.yml) and pick the branch you want to run tests against.
+To run locally, export `AWS_PROFILE` environment variable and run `make e2e tests`. To run from GitHub Actions, use [run-e2e-tests workflow](https://github.com/awslabs/aws-lambda-powertools-python/actions/workflows/run-e2e-tests.yml) and pick the branch you want to run tests against.
+
+**NOTE**: E2E tests are run as part of each merge to `develop` branch.
 
 > **Q: What if there's an error?**
 To be agreed
@@ -182,7 +183,7 @@ To be agreed
 
 Firstly, make sure you are using the `develop` branch and it is up to date with the origin.
 
-There are four main steps to release a new version: Changelog generation, version bumping, and drafting release notes.
+There are three main steps to release a new version: Changelog generation, version bumping, and drafting release notes.
 
 #### Changelog generation
 

tests/e2e/utils/infrastructure.py

@@ -22,7 +22,7 @@ class PythonVersion(Enum):
     V39 = {"runtime": Runtime.PYTHON_3_9, "image": Runtime.PYTHON_3_9.bundling_image.image}
 
 
-class InfrastructureStackInterface(ABC):
+class BaseInfrastructureStack(ABC):
     @abstractmethod
     def synthesize() -> Tuple[dict, str]:
         ...
@@ -32,7 +32,7 @@ def __call__() -> Tuple[dict, str]:
         ...
 
 
-class InfrastructureStack(InfrastructureStackInterface):
+class InfrastructureStack(BaseInfrastructureStack):
     def __init__(self, handlers_dir: str, stack_name: str, config: dict) -> None:
         self.stack_name = stack_name
         self.handlers_dir = handlers_dir
@@ -123,7 +123,7 @@ def __init__(self, stack_name: str, handlers_dir: str, config: dict) -> None:
         self.handlers_dir = handlers_dir
         self.config = config
 
-    def deploy(self, Stack: Type[InfrastructureStackInterface]) -> Dict[str, str]:
+    def deploy(self, Stack: Type[BaseInfrastructureStack]) -> Dict[str, str]:
 
         stack = Stack(handlers_dir=self.handlers_dir, stack_name=self.stack_name, config=self.config)
         template, asset_root_dir, asset_manifest_file = stack()