Skip to content
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

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

Open
matt-primrose opened this issue Sep 12, 2023 · 1 comment
Open

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

matt-primrose opened this issue Sep 12, 2023 · 1 comment
Assignees
Labels
P2 Priority 2 - Medium Tech Debt

Comments

@matt-primrose
Copy link
Contributor

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

@matt-primrose matt-primrose converted this from a draft issue Sep 12, 2023
@matt-primrose matt-primrose moved this to In Progress in Sprint Planning Sep 12, 2023
@bwendlandt-intel bwendlandt-intel moved this from 🆕 New to 📋 Backlog in Feature Backlog Sep 14, 2023
@madhavilosetty-intel madhavilosetty-intel moved this from 📋 Backlog to 🏗 In progress in Feature Backlog Sep 19, 2023
@mechris1
Copy link

mechris1 commented Oct 3, 2023

Code is done, doing some refactoring.

@mechris1 mechris1 moved this from In Progress to Backlog in Sprint Planning Feb 27, 2024
@matt-primrose matt-primrose added the P2 Priority 2 - Medium label Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Priority 2 - Medium Tech Debt
Projects
Status: Backlog
Development

No branches or pull requests

3 participants