open-amt-cloud-toolkit / rpc-go

The Remote Provisioning Client (RPC) communicates with the Manageability Engine Interface (MEI) and Remote Provisioning Service (RPS) interfaces.
https://open-amt-cloud-toolkit.github.io/docs/
Apache License 2.0
13 stars 15 forks source link

[RPC-GO] List of flags is overwhelming for activate command #220

Open matt-primrose opened 1 year ago

matt-primrose commented 1 year ago

Break it out for local vs remote Need to validate parameters for local vs remote (i.e. -ccm is allowed when specifying remote activation) To keep it consistent, do the same for deactivate command too. go run ./cmd/main.go activate -acm activate in admin control mode (ACM) -amtPassword string amt password -ccm activate in client control mode (CCM) -config string specify a config file -d string dns suffix override -h string hostname override -json JSON output -l string Log level (panic,fatal,error,warn,info,debug,trace) (default "info") -lmsaddress string LMS address. Can be used to change location of LMS for debugging. (default "localhost") -lmsport string LMS port (default "16992") -local activate amt locally -n Skip Websocket server certificate verification -name value friendly name to associate with this device -p string Proxy address and port -password string AMT password -profile string name of the profile to use -provisioningCert string provisioning certificate -provisioningCertPwd string provisioning certificate password -t duration AMT timeout - time to wait until AMT is ready (ex. '2m' or '30s') (default 2m0s) -tenant string TenantID -token string JWT Token for Authorization -u string Websocket address of server to activate against -v Verbose output exit status 28

mechris1 commented 1 year ago

Code is done, doing some refactoring.