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.

Sign up for GitHub

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

Jump to bottom

Client should be able to know checks and associate errors to these checks #19

Closed
Tracked by #4454
feloy opened this issue Oct 20, 2023 · 0 comments · Fixed by #27
Closed
Tracked by #4454

Client should be able to know checks and associate errors to these checks #19

feloy opened this issue Oct 20, 2023 · 0 comments · Fixed by #27
Assignees
@feloy

Comments

@feloy
Copy link
Contributor

feloy commented Oct 20, 2023

For the client to be able to list the checks that are being executed, and to associate errors to checks:

  • a command (for example doa list-checks) should return the list of checks supported by the tool[1]
  • the analyze command should associate each error with a check[2]

[1] list of checks

$ doa list-checks -o json
[
  { "name": "user", "description": "Container User" },
  { "name": "port", "description": "Container Exposed port" },
  [...]
]

[2] analyze result

$ doa analyze -f Dockerfile -o json
[
  { "check": "user", "message": "USER directive set to root in parent image parent1" },
  { "check": "user", "message": "USER directive set to root" },
  { "check": "port", "message": "port 80 exposed at line 28 could be wrong. TCP/IP port numbers below 1024 are privileged port numbers" },
  [...]
]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@feloy feloy

Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@jeffmaury @feloy