From a42fd929cc337372c6370ba3a267897f0267d27e Mon Sep 17 00:00:00 2001 From: Dominik Schubert Date: Thu, 9 Nov 2023 07:25:47 +0100 Subject: [PATCH] add sfn v3 note & config update --- content/en/references/configuration.md | 4 ++-- content/en/user-guide/aws/stepfunctions/index.md | 8 ++++++++ 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/content/en/references/configuration.md b/content/en/references/configuration.md index a78f0295bb..aefe933510 100644 --- a/content/en/references/configuration.md +++ b/content/en/references/configuration.md @@ -206,8 +206,7 @@ Please consult the [migration guide]({{< ref "user-guide/aws/lambda#migrating-to | Variable | Example Values | Description | | - | - | - | -| `STEPFUNCTIONS_LAMBDA_ENDPOINT` | `default` | URL to use as the Lambda service endpoint in Step Functions. By default this is the LocalStack Lambda endpoint. Use default to select the original AWS Lambda endpoint. | -| `PROVIDER_OVERRIDE_STEPFUNCTIONS` | `v2` | Activate the new LocalStack-native StepFunctions provider. | +| `PROVIDER_OVERRIDE_STEPFUNCTIONS` | `legacy` / `v2` (default) | The new LocalStack-native StepFunctions provider (v2) is active by default since LocalStack 3.0. | ### SQS @@ -327,6 +326,7 @@ These configurations are deprecated and will be removed in the upcoming major ve | `MOCK_UNIMPLEMENTED` | | **Deprecated.** Whether to return mocked success responses (instead of 501 errors) for currently unimplemented API methods | `ACTIVATE_NEW_POD_CLIENT` | `0`\|`1` (default) | **Deprecated.** Whether to use the new Cloud Pods client leveraging LocalStack container's APIs. | | `BIGDATA_MONO_CONTAINER` | `0`\|`1` (default) | **Deprecated.** Whether to spin Big Data services inside the LocalStack main container. Glue jobs breaks when using `BIGDATA_MONO_CONTAINER=0`. | +| `STEPFUNCTIONS_LAMBDA_ENDPOINT` | `default` | This is only supported for the `legacy` provider. URL to use as the Lambda service endpoint in Step Functions. By default this is the LocalStack Lambda endpoint. Use default to select the original AWS Lambda endpoint. | ## Profiles diff --git a/content/en/user-guide/aws/stepfunctions/index.md b/content/en/user-guide/aws/stepfunctions/index.md index 091ee0816e..cb7e046002 100644 --- a/content/en/user-guide/aws/stepfunctions/index.md +++ b/content/en/user-guide/aws/stepfunctions/index.md @@ -5,6 +5,14 @@ description: > Get started with Step Functions on LocalStack --- + +{{< alert title="Note" >}} +A new [StepFunctions]({{< ref "user-guide/aws/lambda" >}}) implementation is now active by default since LocalStack 3.0 (Docker `latest` since 2023-09-11). + +If you experience any issues please open an issue on GitHub. +You can revert to the old behavior in the meantime by setting `PROVIDER_OVERRIDE_STEPFUNCTIONS=legacy` +{{}} + Step Functions is a serverless workflow engine that enables the orchestrating of multiple AWS services. It provides a JSON-based structured language called Amazon States Language (ASL) which allows to specify how to manage a sequence of tasks and actions that compose the application's workflow. Thus making it easier to build and maintain complex and distributed applications. Step Functions allows for the definition of both standard and express workflows for long-running and high-volume event processing. LocalStack supports Step Functions via the Community offering, allowing you to use the Step Functions APIs in your local environment to create, execute, update, and delete state machines locally. The supported APIs are available on our [API coverage page](https://docs.localstack.cloud/references/coverage/coverage_stepfunctions/), which provides information on the extent of Step Function's integration with LocalStack.