testcontainers / testcontainers/testcontainers-python
`localstack/localstack:latest` will require auth token from March 23 — LocalStack module docs & examples need updating
Nessuno ha ancora preso questa issue.
- Lingua principale
- Python
- Stelle
- 2.3k
- Fork
- 386
- Merge medio
- 4h 40m
- PR unite (30g)
- 1
Descrizione
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! 🙏
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia dalla documentazione del modulo LocalStack e dagli esempi in modules/localstack, quindi leggi la classe LocalStackContainer per comprendere la configurazione attuale dell’immagine e dell’ambiente. Controlla .github/workflows/ci-community.yml per i test basati su LocalStack. Il lavoro è completo quando la documentazione interessata, le indicazioni per la configurazione del container e le aspettative della CI tengono conto dei requisiti di LOCALSTACK_AUTH_TOKEN.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- docker, python
- Ambito
- devops, documentation
- Tipo di issue
- Documentazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 52/100