Skip to content

Latest commit

 

History

History
34 lines (22 loc) · 1.52 KB

File metadata and controls

34 lines (22 loc) · 1.52 KB

Plant Based Pizza Kitchen Service

High Level Architecture Diagram

Pre-requisites

Before deploying the Kitchen stack, you can either cdk deploy the shared infrastructure code. IMPORTANT! This will create an application load balancer and may incur costs. Alternatively, create an SSM parameter named /shared/jwt-key.

Development

The CDK code used to deploy the main application, is split down into two custom L3 constructs. Api and BackgroundWorker. These constructs are used in the main CDK stack, KitchenStack. This is used to deploy the application to actual environments, for example dev and prod.

The CDK constructs are also used in the IntegrationStack. This stack is used for running integration tests, and can be used as part of your development workflow.

To deploy the kitchen services into your account, run the below commands:

# Optionally set these two variables to be a custom suffix, I like to use my initials.
export VERSION="je"
export ENV="je"

# Set this to false if you want to test authorization
export INTEGRATION_TEST="true"

# If you want to use Datadog, store your API key in AWS Secrets Manager and set this secret name variable
export DD_API_KEY_SECRET_NAME=""
cdk deploy KitchenTestStack-${ENV}

Once deployed, you can run integration tests against the deployed resources:

npm run test integration-test