You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-17Lines changed: 1 addition & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ The Loan Broker application with AWS Step Functions, DynamoDB, Lambda, SQS, and
18
18
- Loan Broker routes the application to multiple banks, and the banks reply if they are willing to offer.
19
19
- Loan Broker aggregates all the result(s) and returns the result(s) to the user.
20
20
21
-
Users can deploy this application on LocalStack and AWS with no changes using Cloud Development Kit (CDK). To test this application sample, we will demonstrate how you use LocalStack to deploy the infrastructure on your developer machine and your CI environment. Furthermore, we will showcase how you can use Cloud Pods Launchpad to inject a Cloud Pod into your running LocalStack container to test the application without creating your infrastructure again!
21
+
Users can deploy this application on LocalStack and AWS with no changes using Cloud Development Kit (CDK). To test this application sample, we will demonstrate how you use LocalStack to deploy the infrastructure on your developer machine and your CI environment.
22
22
23
23
## Architecture diagram
24
24
@@ -160,22 +160,6 @@ This application sample hosts an example GitHub Action workflow that starts up L
160
160
161
161
Users can adapt this example workflow to run in their own CI environment. LocalStack supports various CI environments, including GitHub Actions, CircleCI, Jenkins, Travis CI, and more. You can find more information about the CI integration in the [LocalStack documentation](https://docs.localstack.cloud/user-guide/ci/).
162
162
163
-
## Cloud Pods
164
-
165
-
[Cloud Pods](https://docs.localstack.cloud/user-guide/tools/cloud-pods/) are a mechanism that allows you to take a snapshot of the state in your current LocalStack instance, persist it to a storage backend, and easily share it with your team members.
166
-
167
-
You can convert your current AWS infrastructure state to a Cloud Pod using the `localstack` CLI. Check out our [Getting Started guide](https://docs.localstack.cloud/user-guide/tools/cloud-pods/getting-started/) and [LocalStack Cloud Pods CLI reference](https://docs.localstack.cloud/user-guide/tools/cloud-pods/pods-cli/) to learn more about Cloud Pods and how to use them.
168
-
169
-
To inject a Cloud Pod that contains the infrastructure for this application, you can run the following command:
170
-
171
-
```sh
172
-
localstack pod load file://$(pwd)/cloud-pod/loan-broker-application
173
-
```
174
-
175
-
Alternatively, you can use [Cloud Pods Launchpad](https://docs.localstack.cloud/user-guide/tools/cloud-pods/launchpad/) to quickly inject Cloud Pods into your running LocalStack container. Click on the [badge] to launch Cloud Pods Launchpad and inject the Cloud Pod for this application by clicking the `Inject` button.
176
-
177
-
You can use the [LocalStack Web Application](https://app.localstack.cloud) to view the [Step Functions Resource Browser](https://app.localstack.cloud/resources/stepfunctions) and see the State Machine that the Cloud Pod injected. Similarly, you can navigate to the [DynamoDB](https://app.localstack.cloud/resources/dynamodb) to see the `LoanBrokerBanksTable` table, alongside [Lambda functions](https://app.localstack.cloud/resources/lambda), [SNS topic](https://app.localstack.cloud/resources/sns), [SQS queue](https://app.localstack.cloud/resources/sqs), and more that the Cloud Pod injected.
178
-
179
163
## Contributing
180
164
181
165
We appreciate your interest in contributing to our project and are always looking for new ways to improve the developer experience. We welcome feedback, bug reports, and even feature ideas from the community.
0 commit comments