Merge pull request #13 from CodingNagger/feature/nuke

Nuclear option

Author: Andrea-Scuderi

Makefile

@@ -190,6 +190,17 @@ invoke_lambda:
 create_s3_bucket:
 	aws s3 mb "s3://$(AWS_BUCKET)" --profile $(AWS_PROFILE)
 
+delete_s3_bucket:
+	aws s3 ls "s3://$(AWS_BUCKET)" 2>/dev/null >/dev/null && aws s3 rb "s3://$(AWS_BUCKET)" --force 
+
+delete_layer: 
+	aws lambda list-layer-versions --layer-name nio-swift-lambda-runtime-5-1 --output text | \
+		awk '{ print $$NF }' | \
+		xargs aws lambda delete-layer-version --layer-name $(SWIFT_LAMBDA_LIBRARY) --version-number
+
+nuke: clean_layer clean_lambda delete_layer
+	-aws lambda get-function --function-name $(LAMBDA_FUNCTION_NAME) 2>/dev/null >/dev/null && aws lambda delete-function --function-name $(LAMBDA_FUNCTION_NAME) 
+
 #quick commands - no clean
 quick_build_lambda: build_lambda create_build_directory
 	zip -r -j $(LAMBDA_BUILD_PATH)/$(LAMBDA_ZIP) $(SWIFT_PROJECT_PATH)/.build/$(SWIFT_CONFIGURATION)/$(SWIFT_EXECUTABLE)

README.md

@@ -212,7 +212,7 @@ Steps:
 
 There are many ways to achieve a lambda deployment (AWS Console, SAM, CloudFormation ...), please refer to the latest [AWS Lambda documentation](https://docs.aws.amazon.com/lambda/latest/dg/welcome.html) to know more.
 
-#### Requirements
+## Requirements
 
 - an AWS account for test purpose.
 - aws cli: Install the aws cli. Here the [instructions](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html).
@@ -244,7 +244,7 @@ Datetime based versions are created and uploaded to S3 every time your version i
 make upload_lambda_layer
 ```
 
-#### 2) Create the Lambda
+### 2) Create the Lambda
 
 You can create a new lambda which might take a few minutes using one of the options below:
 
@@ -277,7 +277,7 @@ The lambda is created with the following parameters:
 
 This step is required once, if you need to update the lambda use the step 5.
 
-#### 4) Invoke the Lambda
+### 4) Invoke the Lambda
 Now the lambda function is ready for testing. The following command invokes the lambda with using the file **event.json** contained in the project folder.
 
 ```console
@@ -301,7 +301,7 @@ Note:
 
 The lambda invocation may require some policy to access other AWS Resources. Check the `S3Test` example to know more.
 
-#### 5) Update the Lambda (optional)
+### 5) Update the Lambda (optional)
 
 If needed, you will also be able to update your Lambda using one of the commands below:
 
@@ -317,6 +317,24 @@ make update_lambda_with_s3
 make update_lambda
 ```
 
+### 6) Nuclear option
+
+Sometimes you want to go back to a clean slate and we have a command for that which will rely on the parameters you use.
+
+```console
+make nuke
+```
+
+That command will clean your local build folders then delete lambdas and layers created based off the configuration you use.
+
+### 7) Delete S3 bucket
+
+You can delete the S3 bucket where you hold your lambdas and layers with the command below:
+
+```console
+make delete_s3_bucket
+```
+
 # Update the lambda layer
 
 The docker image could require security updates or could require updates.