Enhancement: Please pass raw certificate in json output of `step certificate inspect`

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

维护者通常 1 天内回复

@FoXeNe 已经在做这个了。

开始于 2026年10月26日。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
go

调研方向

Start by locating the implementation and tests for step certificate inspect and its JSON output. Trace how the input certificate is parsed and represented, then define completion as the raw PEM certificate being available in JSON while preserving existing inspection fields and behavior.

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

描述

enhancement needs triage

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

We have Tekton pipelines that filter our certs and CAs based on security criteria and distributes them via AWS/S3, Vault, etc. Our current process uses a combination of awk to parse the certs and then process them though step certificate inspect | jq ... to traffic cop the certs to their destinations. We'd could reduce our scripts/processes to one line invocations of step and jq to validate the input certs (in pem format in our case) filter via jq, and then to create one or more output files IF the pem formated cert was available in the json output.

Why is this needed?

  1. Simplify our pipelines
  2. Less chance for error
  3. Greater ability to filter certs based on all of the possible criteria from a parsed cert (key length, expiration date, usages, etc)

Step certificate inspect is our Swiss Army knife for deploying certs and verifying the endpoints after deployment.

主要语言
Go
星标
4.3k
派生
320
平均合并
2 天 3 小时
30 天内合并 PR
11

环境准备

从这里开始

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

smallstep/cli 的其他 Issue

查看 smallstep/cli 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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