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

Add security scan command #81

Closed
tkilias opened this issue Oct 28, 2021 · 0 comments
Closed

Add security scan command #81

tkilias opened this issue Oct 28, 2021 · 0 comments
Assignees
Labels
refactoring Code improvement without behavior change

Comments

@tkilias
Copy link
Collaborator

tkilias commented Oct 28, 2021

Background

  • We need a way to get informed about packages with vulnerabilities
  • This should be possible for every flavor
  • However, depending on the flavor we might need different tools
  • We want to run the security scan mainly for the release step

Acceptance Criteria

  • We can run security scan for the release step
  • The flavor defines what is running security scan, because this can be different depending on language or package manager

Design idea

  • Flavor defines a separate build step which install the scan tools and runs the scan
  • The scan build step is based on the release step image (FROM {{ release_image_name }})
  • Exaslct implements a new command for the scan of the release image
  • parameter to ignore missing security scan build step to allow gradual migration
@redcatbear redcatbear added refactoring Code improvement without behavior change source:exasol labels Nov 8, 2021
@tomuben tomuben self-assigned this Nov 18, 2021
tomuben added a commit that referenced this issue Nov 30, 2021
@tomuben tomuben closed this as completed in da1f990 Dec 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Code improvement without behavior change
Projects
None yet
Development

No branches or pull requests

3 participants