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
Organize config list #9654
Organize config list #9654
Conversation
As discussed in the Lambda team. It is supported again and we currently have no alternative. Specifically, `LOCALSTACK_HOST` does not support this scenario (yet).
@@ -47,8 +47,6 @@ awslocal kinesis list-streams | |||
} | |||
``` | |||
|
|||
**UPDATE**: Use the environment variable `$LOCALSTACK_HOSTNAME` to determine the target host inside your Lambda function. See [Configuration](#configuration) section for more details. |
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.
@HarshCasper Are these outdated READMEs under docs still relevant here. Maybe we should remove them and link to our documentation page instead?
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, seems to make sense to include the legacy config here as well.
Thanks for continuing to support the effort of improving our config management. Really looking forward to give this more structure in the future 👍
# Note: do *not* include DATA_DIR in this list, as it is treated separately | ||
# => Synchronize this list with the above and the configuration docs: | ||
# https://docs.localstack.cloud/references/configuration/ | ||
# => Sort this list alphabetically |
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.
good hint! definitely a piece of knowledge that was mostly just lived through tradition but it's good to have this written down here
Motivation
localstack.config.py
has become bloated by mixing up deprecated, removed, and current configurations.HOSTNAME_FROM_LAMBDA
is deprecated but still supported.Changes
This PR primarily improves the organization of the config list and removes a deprecation:
HOSTNAME_FROM_LAMBDA
from deprecations. This was deprecated but then added to the new Lambda provider upon request. The Lambda team decided to un-deprecate it given the need and currently no supported alternatives.AWS_ENDPOINT_URL
LOCALSTACK_HOSTNAME