Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add programmatic configuration

未关闭
#1,569 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker, node.js, typescript
领域
tooling

调研方向

Start with packages/testcontainers/src/test-containers.ts and packages/testcontainers/src/testcontainers-runtime/strategies/utils/config.ts, then trace the listed process.env reads in the reaper, port forwarder, image name, generic container and auth paths. Define how configuration is resolved alongside environment variables and the properties file, including precedence and changes after runtime initialization. Done means TestContainers.configure() and getConfiguration() provide typed effective settings while existing configuration sources continue to work.

由索引模型根据 Issue 内容生成。

描述

enhancement minor

What happens

Configuration comes only from environment variables and .testcontainers.properties, and each setting is read where it is used. Fourteen variables are read through process.env across packages/testcontainers/src (Ryuk image, port, privileged, verbose and disabled flags, the SSHD image and port, the hub image prefix, reuse, Docker auth config and others), plus the Docker host settings in the strategy config.

  • Changing a setting from code means assigning to process.env before the first container starts.
  • Nothing is typed or validated. A misspelt variable is silently ignored.
  • There is no way to read the effective configuration.

Expected

A typed configuration object with one place that resolves it:

TestContainers.configure({
  ryuk: { disabled: false, privileged: true },
  hubImageNamePrefix: "registry.example.com/mirror",
  reuse: { enabled: true },
});
  • Environment variables and the properties file keep working, with a documented precedence.
  • TestContainers.getConfiguration() returns what is in effect.

Where

  • packages/testcontainers/src/container-runtime/strategies/utils/config.ts
  • the process.env reads in reaper/reaper.ts, port-forwarder/port-forwarder.ts, container-runtime/image-name.ts, generic-container/generic-container.ts and container-runtime/auth/
  • packages/testcontainers/src/test-containers.ts

Notes

  • Java centralises this in TestcontainersConfiguration.
  • Configuration must be set before the runtime client and Ryuk are created. Decide what happens when it is changed afterwards.

Dependencies

  • Nothing blocks this. It can start now.
  • Coordinate with #1568: the logger is a natural configuration setting.
主要语言
TypeScript
星标
2.6k
派生
274
平均合并
1 天 14 小时
30 天内合并 PR
44

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

testcontainers/testcontainers-node 的其他 Issue

查看 testcontainers/testcontainers-node 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。