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

proposal: per-lease provider options

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
8/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
typescript
领域
api

调研方向

This is a design proposal, not a task. Start by reading the hard-coded provider fields in packages/contracts/src/remote-config-fields.ts (around line 28) and how they reach the core client contract. The proposed leases.allocate({ leaseProvider, providerOptions }) API and plugin validation are still undecided. Done would be an agreed design, not a patch; coordinate with the maintainers first.

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

描述

backlog enhancement needs-triage

Part of #3747. Proposal; not scheduled.

Problem

  • Provider options are hard-coded into core. Provider-specific request options are fixed fields of the core client contract (packages/contracts/src/remote-config-fields.ts:28: awsProjectArn, providerApp, …).
  • Nothing provider-specific reaches a single lease. Instance identity and credentials therefore belong to the whole daemon. That's why e2e runs one daemon per worker.

Proposal

  • The API. leases.allocate({ leaseProvider, providerOptions }), validated by the plugin. It would replace the hard-coded fields.
  • What it would allow:
    • one daemon serving many workers;
    • @agent-device/limrun owning instance creation: model, OS version, timeout and labels.

Status

This needs a design pass before it's scheduled. It must not block #3755 or #3757.

主要语言
TypeScript
星标
5k
派生
334
平均合并
12 小时 2 分钟
30 天内合并 PR
678

环境准备

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

从这里开始

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

callstack/agent-device 的其他 Issue

查看 callstack/agent-device 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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