add build time service catalog cache generation to s3 image #12341
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8000
bentsku
approved these changes
Mar 5, 2025
alexrashed
added a commit
to localstack/localstack-cli
that referenced
this pull request
Mar 5, 2025
With #33 a workaround was introduced to avoid issues with `localstack status services` right after starting the community edition. This workaround is removed since the issue has been fixed with localstack/localstack#12341
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
#12314 introduced a docker-build-time generation of the service catalog cache.
Unfortunately, I forgot about the
Dockerfilefor the S3 image.Changes
Dockerfile.