David Tesar
David Tesar
As a signer, I want to remote sign remote artifacts stored in registries, so that the integrity of the artifacts is ensured as artifacts are pulled and promoted across environments....
As a user, I want to list the plugin(s) so that I can view the installed plugin(s) Implementation items to track: - [ ] https://github.com/notaryproject/notation/issues/230
CLI implementation for the tag to digest translation.
Request by @priteshbandi in https://github.com/notaryproject/notation/issues/93 Instead of exporting types can we export routines so that underlying implementation can be changed without affecting callers? https://github.com/notaryproject/notation/pull/83#discussion_r709484002
As a user, I want to add/update/list/delete keys Implementation items to track: - [ ] https://github.com/notaryproject/notation/issues/226
As a user, I want to push signatures into remote registry, using tag or digest references Note: decision by group to push past RC-1, since notation sign does push automatically,...
As a user, I want to pull signatures from remote registry, using tag or digest references Note: decision by group to push past RC-1, since notation verify does pull automatically,...
As a signer, I want to use an extensible plugin to sign the artifacts As a verifier, I want to use extensible plugin to verify signed artifacts - [ ]...
the [os.UserConfigDir()](https://github.com/notaryproject/notation/blob/c61102cdb414a9aa55980bd113496abef3fcf784/pkg/config/path.go#L59) varies and therefore isn't the same based on OS. i.e. on Ubuntu `~/.config/notation/plugins/azure-kv` works fine. on a mac it is `~/Library/Application Support/notation/plugins`
Currently `notation plugin` only officially supports the `list` command. It is confusing, error prone, and time consuming for users to have to go lookup what the proper directory is for...