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

spec: add CLI notation certificate and key specs #361

Merged
merged 22 commits into from
Oct 19, 2022

Conversation

yizha1
Copy link
Contributor

@yizha1 yizha1 commented Sep 28, 2022

No description provided.

@yizha1 yizha1 added the cli Issue or PR released to Notation CLI label Sep 28, 2022
@yizha1 yizha1 added this to the RC-1 milestone Sep 28, 2022
@yizha1 yizha1 self-assigned this Sep 28, 2022
@yizha1 yizha1 changed the title spec: Add CLI notation certificate and key specs spec: add CLI notation certificate and key specs Sep 28, 2022
-d, --default mark as default
-h, --help help for generate-test
-n, --name string key and certificate name
--trust add the generated certificate to the trust store
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we have trust policy and trust store, we need to elaborate what --trust means.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the description is clear for --trust. Do you mean we need to change the name of --trust for trust store only? For example --trust-store?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This flag only adds the generated certificate to the trust stone, no operations on trust policy.

@codecov-commenter
Copy link

codecov-commenter commented Oct 10, 2022

Codecov Report

Merging #361 (020b53b) into main (6e8e9c5) will increase coverage by 1.49%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #361      +/-   ##
==========================================
+ Coverage   30.54%   32.03%   +1.49%     
==========================================
  Files          25       26       +1     
  Lines        1614     1670      +56     
==========================================
+ Hits          493      535      +42     
- Misses       1108     1122      +14     
  Partials       13       13              
Impacted Files Coverage Δ
cmd/notation/push.go 21.91% <0.00%> (-2.70%) ⬇️
internal/cmd/flags.go 52.74% <0.00%> (-1.80%) ⬇️
internal/cmd/signer.go 0.00% <0.00%> (ø)
internal/cmd/options.go 0.00% <0.00%> (ø)
cmd/notation/cert_gen.go 0.00% <0.00%> (ø)
internal/envelope/envelope.go 100.00% <0.00%> (ø)
cmd/notation/verify.go 26.89% <0.00%> (+8.26%) ⬆️
cmd/notation/sign.go 42.45% <0.00%> (+12.56%) ⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@yizha1 yizha1 requested a review from gokarnm October 11, 2022 09:01
@priteshbandi priteshbandi removed this from the RC-1 milestone Oct 12, 2022
Copy link
Contributor

@patrickzheng200 patrickzheng200 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Update key in signing key list

Usage:
notation key update [flags] <key_name>
Copy link
Contributor

@priteshbandi priteshbandi Oct 19, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whats the purpose/ intended use of update command? Is it just to update default key? if so, the --default flag becomes mandatory here.

Also, if it its only for updating default key, should we rename it to update-default ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently only one flag '--default', there could be more later.

@yizha1 yizha1 requested a review from priteshbandi October 19, 2022 12:55
Copy link
Contributor

@shizhMSFT shizhMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@priteshbandi priteshbandi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@priteshbandi priteshbandi merged commit 193a533 into notaryproject:main Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli Issue or PR released to Notation CLI
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

7 participants