Description
Currently, rpc-go requires admin privileges even for commands like version, which should not require elevation. As part of v3, we should improve this behavior so users can run basic informational commands without needing admin privileges.
There are also a few useful details missing today that customers often ask for while debugging, such as:
- When that build of
rpc-go was created
The goal is to allow rpc-go to show basic information without requiring admin access, while still showing additional privileged information only when the command is run with admin privileges.
Examples:
version should work without admin privileges
amtinfo should show non-privileged/basic information without admin privileges
- Detailed device/system information can continue to be shown only when run with admin privileges
Acceptance Criteria
Description
Currently,
rpc-gorequires admin privileges even for commands likeversion, which should not require elevation. As part of v3, we should improve this behavior so users can run basic informational commands without needing admin privileges.There are also a few useful details missing today that customers often ask for while debugging, such as:
rpc-gowas createdThe goal is to allow
rpc-goto show basic information without requiring admin access, while still showing additional privileged information only when the command is run with admin privileges.Examples:
versionshould work without admin privilegesamtinfoshould show non-privileged/basic information without admin privilegesAcceptance Criteria
versionworks without requiring admin privileges.rpc-godisplays build-related information such as version and build time/date.amtinfoshows basic/non-privileged information when run without admin privileges.rpc-gois run with admin privileges.