Support storing/securing SSH keys in Vault

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

The issue names no files, tests or entry points. Start by finding where OpenBot currently reads SSH keys and other credentials from disk or environment variables, and check whether any existing secret-provider hook exists. Done would mean a written proposal from a maintainer on whether to add Vault support or document an existing path, since the request asks for either and rotation without redeploy is a design question.

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

描述

Feature Request

We need to store our SSH keys securely using HashiCorp Vault instead of keeping them in plain config/files.

Could you add support (or document the existing way, if already possible) for:

  • Storing an SSH private key as a secret in Vault
  • Having OpenBot fetch the SSH key from Vault at runtime instead of reading it from disk/env
  • Rotating the key in Vault without requiring a redeploy

This would improve credential security for self-hosted/server deployments. Happy to provide more details on our setup if helpful.

主要语言
TypeScript
星标
9.2k
派生
1.2k
平均合并
2 天 20 分钟
30 天内合并 PR
135

环境准备

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

从这里开始

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

CopilotKit/OpenBot 的其他 Issue

查看 CopilotKit/OpenBot 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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