You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to allow Prowler to be installed just for an specific provider without the need of installing all the providers dependencies.
Currently the package installed contains the evaluations for all the providers regardless of where exactly the scans are going to be run. e.g. If a user wants to use Prowler to scan an AWS environment, the install process should skip installing the relevant checks for Azure, GCP or other providers.
This will help reduce the install size and also speed up the installation times.
Solution Proposed
A flag / parameter can be added that the user can supply at install time, like pip install prowler[<provider>].
Describe alternatives you've considered
Workaround to install Prowler in the AWS CloudShell service due to the storage limitation:
New feature motivation
We want to allow Prowler to be installed just for an specific provider without the need of installing all the providers dependencies.
Currently the package installed contains the evaluations for all the providers regardless of where exactly the scans are going to be run. e.g. If a user wants to use Prowler to scan an AWS environment, the install process should skip installing the relevant checks for Azure, GCP or other providers.
This will help reduce the install size and also speed up the installation times.
Solution Proposed
A flag / parameter can be added that the user can supply at install time, like
pip install prowler[<provider>]
.Describe alternatives you've considered
Workaround to install Prowler in the AWS CloudShell service due to the storage limitation:
Thanks to @jchrisfarris 🙌
Additional context
No response
The text was updated successfully, but these errors were encountered: