Dominik Schubert

@alexrashed what's your take on it, should we continue here or just close if for now? Haven't seen any push in that direction so I'd say it's not super urgent

Hi @Chad-Bailer-Regal ! The specific issue you reported should be fixed now and not block the second deploy anymore. In your specific sample though the `--resolve-image-repos` flag you're using on...

> @dominikschubert that's great! is the fix in the latest image already? Yes this is available via both the latest tagged images of `localstack/localstack` and `localstack/localstack-pro`

Hi @jsteenb2 ! You can use our `LAMBDA_RUNTIME_IMAGE_MAPPING` configuration variable (see https://docs.localstack.cloud/references/configuration/#lambda) to specify custom images (including a custom repo) for the base images that are used to spawn a...

@thrau collecting a few of my findings below, will update with more when I encounter them - ASF generation is broken `FileNotFoundError: [Errno 2] No such file or directory: 'localstack/aws/api/stepfunctions'...

Hi @wbeardall ! > as the provided instructions haven't worked on my machine. Anything we can help with there? What's was the issue exactly?

Another user story for this would be having both image-based and zip-based lambda functions and we don't want the image-based functions to have the S3Uri etc. fields

@Pive01 I've pushed the changes necessary for a single `pyproject.toml` that replaces both `setup.cfg` and `setup.py`. I suggest we'll add some linting/formatting in a follow-up as well, just to make...