-
Notifications
You must be signed in to change notification settings - Fork 86
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
Improve notation plugin error message #867
Comments
If you use a text file as the plugin executable, the OS will return the same error message. Therefore, we may not be able to determine the detailed error of fork/exec, whether it is an OS architecture issue or not. How about error message for notation-go:
And add the suggestion in the CLI side:
|
It seems not feasible to detect the OS/Arch information of the plugin during installation. Therefore, notation can only output generic error message regardless of in which error case under the current implementation. This is not helpful to Is it possible to enable notation detect the OS/Arch information of the plugin during installation in future releases? In this way, we can generate much more actionable suggestions in the error message to users. |
My suggested change for the error message from the
Note that there is no concept "Notation plugin protocol" existed in Notary Project or plugin vendors. In general, plugin vendors and Notary Project maintainers publish the plugin installation requirements on the website. So the most straightforward way here is to remind users to re-check and follow the plugin installation requirements accordingly. |
How about this error message for Notation CLI? We can provide the OS and Arch in the recommandation. |
The prompted recommendation in |
- added `PluginUnknownError`, `PluginValidityError`, `PluginDirectoryError`. For each error types, Notation CLI should provide a recommanded suggestion to solve them. - improved error message Resolve part of: notaryproject/notation#824 Resolve part of: notaryproject/notation#867 Signed-off-by: Junjie Gao <[email protected]> --------- Signed-off-by: Junjie Gao <[email protected]>
What is not working as expected?
This issue summarizes the error messages of
notation plugin
that I suggest improving in v1.1.x.Negative case: install a plugin on a non-matching CPU architecture machine
I installed Notation AKV plugin (Linux_arm64 version) on an Linux_amd64 machine with Notation v1.1.0 (main branch). The error response is empty in stderr as follows. This empty error response also exists when I installed the AWS Signer plugin in a mismatched Arch.
What did you expect to happen?
Suggested change:
By following the Notation error message guidance,
notation
should prompt users that the architecture of the installing plugin is not matched with the machine:Or even give a much intelligent prompt with a solution:
How can we reproduce it?
See above
Describe your environment
Linux, Golang 21.06
What is the version of your notation-go Library?
v1.1.0
The text was updated successfully, but these errors were encountered: