-
Notifications
You must be signed in to change notification settings - Fork 59
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
Adding ability to list attestors #384
Conversation
Signed-off-by: chaosinthecrd <[email protected]>
Signed-off-by: chaosinthecrd <[email protected]>
Signed-off-by: chaosinthecrd <[email protected]>
Definitely a very welcome addition and will become even more necessary as more attestors get added. I do wonder if it's worth giving the Need to run |
So @mikhailswift, you have probably noticed that I deliberately removed Maybe |
This is maybe a useless philosophical perspective for end users but, for me, |
I see both sides and am good either way. I do think adding some logic to handle the case where |
Signed-off-by: chaosinthecrd <[email protected]>
✅ Deploy Preview for witness-project canceled.
|
Signed-off-by: chaosinthecrd <[email protected]>
Signed-off-by: chaosinthecrd <[email protected]>
Signed-off-by: chaosinthecrd <[email protected]>
What this PR does / why we need it
#372 highlights the lack of ability for users to list the attestors that are available for calling when running
witness run
.This PR adds a
witness attestors
subcommand, which allows users to get a list of the attestors available back. In the future we should consider adding descriptions into the attestors in the https://github.com/in-toto/go-witness library and exposing those descriptions here.Executing the command gives an output like: