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

Abierto
  • ¿Algo no está bien?
#1,609 1 comentario 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@FoXeNe ya está trabajando en esto.

Desde el 26/10/2026.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
go
Área
cli, cryptography, security

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
4.3k
Forks
320
Merge medio
2 d 3 h
PR fusionados (30 d)
11

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de smallstep/cli

Todos los issues de smallstep/cli

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.