-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Transit Import Key CLI functionality #18887
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks pretty good!
Are there tests here anywhere?
wrappedTargetKey, err := wrapKWP.Wrap(key) | ||
if err != nil { | ||
c.UI.Error(fmt.Sprintf("failure wrapping source key: %v", err)) | ||
return 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what are your return codes / are they documented somewhere? (in particular 1 vs. 2 vs 3 as failures)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do.
Apparently cli commands don't have unit tests? The actual import algo is covered by the unit tests in transit though. |
Co-authored-by: Steven Clark <[email protected]>
CLI does have unit tests, see e.g., |
Adds transit import/import-key to bring keys into transit and transform via
the key wrapping protocol.