Currently, the image of RapiDAST is quite large (~1.24GB, source). As each team may pull and deploy it in the CI pipeline periodically, this could lead to an increase in execution times and resource costs over time.
It would be great if we could make some optimizations to the Containerfile.
Currently, the image of RapiDAST is quite large (~1.24GB, source). As each team may pull and deploy it in the CI pipeline periodically, this could lead to an increase in execution times and resource costs over time.
It would be great if we could make some optimizations to the Containerfile.
We could start with some general tips, like: