CLI Cmds for trust policy management - phase 1

[yizha1]

What is the areas you would like to add the new feature to?

Notation CLI

Is your feature request related to a problem?

Today the UX of trust policy management is cumbersome and error prone.

• Users need to manually create and edit a JSON file, and there are several parameters user need to properly configure. See trust policy spec.
• The name for the JSON file MUST be trustpolicy.json, and this file needs to be stored in Notation configuration directory, which is different for different OS, see directory structure. It's hard to remember the directory path for different OS.
• The JSON file encoding MUST be utf-8 without BOM. However, for some environments it is not by default. It is error prone.

What solution do you propose?

To improve the UX of managing trust policy and meet Notation v1.0 release goal, a phased approach is proposed. This issue will address the solution for the first phase. The scope for first phase:

• Import trust policy: User can import a trust policy configuration file with arbitrary name into notation, so that users don't need to consider where this file should go to, and what is the name of trust policy file.
• Export trust policy: User can export the trust policy configuration file to local disk, so that user can update it and import it afterwards.
• View trust policy: User can easily view the content of trust policy file.
• template file: Provide a template file of trust policy configuration for users to get started. The template file could be packaged with notation binary together.

What alternatives have you considered?

No

Any additional context?

No response

[yizha1]

As discussed in the slack, update the milestone to RC-3.

[yizha1]

Reopen this issue since implementation is not completed yet. The previous closure is due to spec was merged.

• update CLI spec: doc: create CLI spec for managing trust policies (phase 1) #568
• implementation