Skip to content

Update configuration examples to match common use cases#141

Merged
gtsiolis merged 1 commit intomainfrom
george/update-config-template
Mar 19, 2026
Merged

Update configuration examples to match common use cases#141
gtsiolis merged 1 commit intomainfrom
george/update-config-template

Conversation

@gtsiolis
Copy link
Copy Markdown
Member

@gtsiolis gtsiolis commented Mar 19, 2026

This will update README and default_config.toml configuration examples to reflect how users actually use LocalStack.

See relevant discussions[1][2] with some data points.

  1. debug profile combines commonly used environment variables (DEBUG, PERSISTENCE) and ENFORCE_IAM.
  2. ci profile for loading common services for faster startup in CI using SERVICES and EAGER_SERVICE_LOADING.

@gtsiolis gtsiolis self-assigned this Mar 19, 2026
@gtsiolis gtsiolis force-pushed the george/update-config-template branch from 78e0dbd to c707883 Compare March 19, 2026 11:13
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 19, 2026

Warning

Rate limit exceeded

@gtsiolis has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 24 minutes and 59 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 455c926a-788f-4573-9f18-f98586dd23c1

📥 Commits

Reviewing files that changed from the base of the PR and between c707883 and 8d48665.

📒 Files selected for processing (2)
  • README.md
  • internal/config/default_config.toml
📝 Walkthrough

Walkthrough

This PR updates configuration documentation and examples in README and default config template. Changes include clarifying container semantics with inline comments, adding volume field documentation, updating environment variable examples (SERVICES, EAGER_SERVICE_LOADING), changing container tag from pinned version to latest, and reorganizing environment profile examples from prod/debug to debug/ci.

Changes

Cohort / File(s) Summary
Documentation examples
README.md
Updated "Default config" TOML example with inline comments for type, tag, port, and commented placeholders for volume and env. Added volume field to documentation. Modified "Passing environment variables" example: changed container tag from 4.14.0 to latest, replaced env sets from ["prod", "debug"] to ["debug", "ci"], removed [env.prod] section, expanded [env.debug] with additional variables, and added new [env.ci] section.
Default config template
internal/config/default_config.toml
Updated comments to change ENFORCE_IAM description from "enable IAM enforcement" to "enable IAM policy enforcement," added new commented environment variables (SERVICES, EAGER_SERVICE_LOADING), renamed "Example" section to "Example profiles," and adjusted profile examples to include [env.ci] while removing [env.persist] and [env.security] examples.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • silv-io
  • anisaoshafi
  • carole-lavillonniere
🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Update configuration examples to match common use cases' directly aligns with the primary change: updating README and default_config.toml examples to reflect actual user usage patterns.
Description check ✅ Passed The description clearly relates to the changeset by explaining the rationale for the configuration example updates and detailing the new debug and ci profiles being added.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch george/update-config-template
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gtsiolis gtsiolis force-pushed the george/update-config-template branch from c707883 to 8d48665 Compare March 19, 2026 11:16
Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
README.md (1)

117-119: Consider pinning the image tag in the CI example.

On Line 117, tag = "latest" can make CI runs non-reproducible over time. For the CI-focused example (Lines 126-128), a pinned tag (e.g. date/version) is usually safer and more deterministic.

Also applies to: 126-128

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 117 - 119, Update the CI example to pin the image tag
instead of using tag = "latest": replace the `tag` value in the shown block (the
`tag = "latest"` entry) and the other CI example occurrences so they use a
specific, immutable tag (e.g., a version or date-based tag) to make CI
reproducible; ensure both instances of `tag` in the README are updated
consistently and document the chosen tag format.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@README.md`:
- Around line 117-119: Update the CI example to pin the image tag instead of
using tag = "latest": replace the `tag` value in the shown block (the `tag =
"latest"` entry) and the other CI example occurrences so they use a specific,
immutable tag (e.g., a version or date-based tag) to make CI reproducible;
ensure both instances of `tag` in the README are updated consistently and
document the chosen tag format.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 65637c19-2839-4366-aa07-0b608e601313

📥 Commits

Reviewing files that changed from the base of the PR and between a022cc1 and c707883.

📒 Files selected for processing (2)
  • README.md
  • internal/config/default_config.toml

Copy link
Copy Markdown
Contributor

@anisaoshafi anisaoshafi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Neat, thanks for following up on this 👏🏼

@@ -93,15 +93,18 @@ lstk --config /path/to/lstk.toml start

```toml
[[containers]]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we might want to add the update prompt value here. Or I can just add it in my PR depending on what we merge first :D

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can update the prompt, merging this one.

@gtsiolis gtsiolis merged commit 9b1a4d1 into main Mar 19, 2026
8 checks passed
@gtsiolis gtsiolis deleted the george/update-config-template branch March 19, 2026 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants