testcontainers / testcontainers/testcontainers-python
`localstack/localstack:latest` will require auth token from March 23 — LocalStack module docs & examples need updating
まだ誰も着手していません。
- 主要言語
- Python
- スター
- 2.3k
- フォーク
- 386
- 平均マージ
- 4時間 40分
- マージ済み PR(30日)
- 1
説明
Hey folks 👋
I'm Harsh from the LocalStack team. Wanted to flag an upcoming change that will directly affect users of the LocalStack module in this library.
What's changing: Starting March 23, 2026, localstack/localstack:latest on Docker Hub will consolidate into a single unified image that requires authentication via a LOCALSTACK_AUTH_TOKEN. The free Community image, as it exists today, will no longer be available under that tag without an auth token set.
What this means for this repo:
The LocalStackContainer in modules/localstack pulls localstack/localstack by default to spin up the container during tests. Any user who instantiates LocalStackContainer after March 23 without a LOCALSTACK_AUTH_TOKEN set will hit an authentication error and their tests will fail immediately.
The places most likely to need updating:
- The LocalStack module docs and any related examples in
modules/localstack, which don't currently mention auth token setup as a prerequisite - The
LocalStackContainerclass itself, where passingLOCALSTACK_AUTH_TOKENas an environment variable should be documented or facilitated - The CI/CD pipeline (
.github/workflows/ci-community.yml) if it runs LocalStack-based tests without an auth token
What users will need to do:
- Sign up for a free LocalStack account at [localstack.cloud](https://localstack.cloud/)
- Generate an auth token from the LocalStack Web App
- Set
LOCALSTACK_AUTH_TOKENas an environment variable when starting the container
With testcontainers-python, this would look like:
import os
from testcontainers.localstack import LocalStackContainer
with LocalStackContainer() \
.with_env("LOCALSTACK_AUTH_TOKEN", os.environ.get("LOCALSTACK_AUTH_TOKEN", "")) as localstack:
# your test code here
pass
The good news: A free tier is staying — no one has to pay. CI credits are now unlimited on all plans, including free, and open-source projects like this one can apply for free access to paid plans.
Full details in our announcements:
- https://blog.localstack.cloud/the-road-ahead-for-localstack/
- https://blog.localstack.cloud/localstack-single-image-next-steps/
- https://blog.localstack.cloud/2026-upcoming-pricing-changes/
Happy to help with any doc updates, review PRs, or answer questions. Let us know if there's anything we can do to make this easier — and thanks for maintaining the LocalStack module for the Python community! 🙏
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
まず modules/localstack 配下の LocalStack モジュールのドキュメントと例を確認し、次に LocalStackContainer クラスを読んで、現在のイメージと環境の設定を理解します。.github/workflows/ci-community.yml で LocalStack ベースのテストを確認します。影響を受けるドキュメント、コンテナのセットアップ手順、CI の前提が LOCALSTACK_AUTH_TOKEN の要件に対応していれば完了です。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- docker, python
- 領域
- devops, documentation
- issue の種類
- ドキュメント
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 52/100