-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Step Functions: remove config variables for legacy provided removed in v4.0 #12492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 8m 31s ⏱️ Results for commit 080b4fb. ♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files ±0 2 suites ±0 1h 51m 32s ⏱️ +47s For more details on these errors, see this check. Results for commit 080b4fb. ± Comparison against base commit 7dc21bd. ♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🧹🏠
(kind reminder to adjust/remove these variable in case they appear in any public docs)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add them to deprecations.py
to pro-actively inform the user (requires keeping the list in CONFIG_ENV_VARS
) or is the provider deprecation warning sufficient?
Thank you! I have reported the changes also in |
Motivation
The legacy Step Functions provider was removed in version 4.0. However, some related configuration options,
LOCAL_PORT_STEPFUNCTIONS
andSTEPFUNCTIONS_LAMBDA_ENDPOINT
, were left behind in the codebase. Neither of these environment variables is currently in use. In LocalStack's docsSTEPFUNCTIONS_LAMBDA_ENDPOINT
is already correctly documented as a legacy optionLOCAL_PORT_STEPFUNCTIONS
is not listed.Changes
LOCAL_PORT_STEPFUNCTIONS
andSTEPFUNCTIONS_LAMBDA_ENDPOINT