Skip to content

The verbose log for checking trust policy lacks intuitiveness #430

@yizha1

Description

@yizha1

What is not working as expected?

When using the notation verify command with the flag -v, the following logs will be shown:

INFO Checking whether signature verification should be skipped or not
INFO Trust policy configuration:
INFO Check over. Trust policy is not configured to skip signature verification

The logs indicated that trust policy is being checked to see whether signature verification will be skipped or not. The last log indicated that the check is over. However, the sentence Trust policy is not configured to skip signature verification is not well written, there is a double negative in the sentence, which is not easy to understand.

What did you expect to happen?

Improve the sentence Trust policy is not configured to skip signature verification to make it more intutive.

If trust policy is configured for signature verification, then the log can be

Trust policy is configured for signature verification at level strict.

If trust policy is configured to skip signature verification, then the log can be

Trust policy is configured to skip signature verification.

How can we reproduce it?

Use notation verify command with -v flag.

Describe your environment

Linux OS

What is the version of your notation-go Library?

v1.2.0-beta.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions