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

Aberta
  • Algo errado?
#1,609 1 comentário 1 reação 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@FoXeNe já está trabalhando nisso.

Desde 26/10/2026.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
45/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Stack de tecnologia
go
Domínio
cli, cryptography, security

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Go
Estrelas
4.3k
Forks
320
Merge médio
2d 3h
PRs com merge (30d)
11

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de smallstep/cli

Todas as issues de smallstep/cli

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.