Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: step certificate inspect no longer supports reading cert from piped out put #1173

Closed
a1994sc opened this issue May 9, 2024 · 3 comments
Labels
bug needs triage Waiting for discussion / prioritization by team
Milestone

Comments

@a1994sc
Copy link

a1994sc commented May 9, 2024

Steps to Reproduce

  1. step certificate inspect --format pem --insecure https://github.com > github.pem
  2. step certificate inspect github.pem This works
  3. cat github.pem | step certificate inspect This does not

Your Environment

  • OS - Fedora 39
  • step CLI Version - 0.26.1

Expected Behavior

Read the cert from the piped output

Actual Behavior

gives error reading -: no such file or directory

Additional Context

I have some certs in sops secrets and want to read the alternative names, so I run the following command with 0.26.1 and it errored out

sops -d secret/tls.yml | yq '.stringData."tls.crt"' | step certificate inspect --format json | yq -p=json .names | sort | yq

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@a1994sc a1994sc added bug needs triage Waiting for discussion / prioritization by team labels May 9, 2024
@a1994sc
Copy link
Author

a1994sc commented May 9, 2024

Minor comment, but step 3. does work with 0.25.2

@dopey
Copy link
Contributor

dopey commented May 9, 2024

Hey @a1994sc 👋. Thanks for opening the issue!

I believe this has already been resolved in the default branch - #1162. Should be part of a release within the next few weeks.

@dopey dopey closed this as completed May 9, 2024
@a1994sc
Copy link
Author

a1994sc commented May 9, 2024

Oh, @dopey , sorry I must have missed that when I went looking for issues. Thank you very much! I will keep an eye out for it. For the time being I rolled back my version to 0.25.2

@hslatman hslatman modified the milestones: v0.26.3, v0.26.2 Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs triage Waiting for discussion / prioritization by team
Projects
None yet
Development

No branches or pull requests

3 participants