`localstack/localstack:latest` will require auth token from March 23 — LocalStack module docs & examples need updating

Aberta
#985 12 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
52/100
Tipo de issue
Documentação
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Stack de tecnologia
docker, python
Domínio
devops, documentation

Direção de pesquisa

Comece pela documentação e pelos exemplos do módulo LocalStack em modules/localstack e, em seguida, leia a classe LocalStackContainer para entender sua configuração atual de imagem e ambiente. Verifique .github/workflows/ci-community.yml em busca de testes baseados em LocalStack. Considera-se concluído quando a documentação afetada, as orientações de configuração do contêiner e as expectativas de CI contemplarem os requisitos de LOCALSTACK_AUTH_TOKEN.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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 LocalStackContainer class itself, where passing LOCALSTACK_AUTH_TOKEN as 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:

  1. Sign up for a free LocalStack account at [localstack.cloud](https://localstack.cloud/)
  2. Generate an auth token from the LocalStack Web App
  3. Set LOCALSTACK_AUTH_TOKEN as 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:

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! 🙏

Linguagem predominante
Python
Estrelas
2.3k
Forks
386
Merge médio
4h 40min
PRs com merge (30d)
1

Guia de contribuição

Abrir o guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de testcontainers/testcontainers-python

Todas as issues de testcontainers/testcontainers-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.