I dont think the cli should handle the install steps.
These are already pretty straight forward using helm, creating a custom cli for it seems like a big overhead.

The creating / starting scans seems like a more important usecase to me, as the starting of scans can currently be quite cumbersome, as it requires a scan manifest in the localfiles system. Having a "simple cli" with a "scan" command e.g. scbctl scan nmap scanme.nmap.org would be pretty cool.

We have a convenience script for installation though.

Hello everyone, my name is Thibaut Batale! I'm a final year computer science undergraduate, I'm interested in this project "adding a secureCodeBox CLI" and currently drafting a proposal for it. Just wanted to confirm my thoughts, the main priority commands to build during this term are the create and observe scanners commands. Followed by update and delete scanners commands ...

Hi @Freedisch awesome :)

The prioritise are as described in the issue description.

• create & observe scans
  e.g. scbctl scan amass enum -d example.com to directly create a Scan with a scanType amass and the parameters: ["enum", "-d", "example.com"]. Ideally the cli would also have a paramters to automatically "follow" the scans progress to view the logs of scanner & parser and show a summary of the results.
• directly trigger new executions of ScheduledScans
  e.g. scbctl trigger --namespace internal-scans daily-network-scan to directly trigger a new Scan for the daily-network-scan Scheduled Scan
• interact with cascading rules

Deletion of scans i don't think should be handled by a custom cli as they are already possible to do with a single kubectl delete scan command.
Updating scans isn't really that well supported in the SCB either as scans are a one time thing and aren't reexecuted when the definition for them are changed.