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

Scanning a list GCP projects and combining results into a single report #1583

Open
Spiroman opened this issue Oct 17, 2023 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@Spiroman
Copy link

Is your feature request related to a problem? Please describe.

In the case that I would need to scan 20 out of lets say 100 projects, I wouldn't want to run the scanner on all 100, and at the same time I wouldn't want to have 20 individual reports. Ideally, I'd have 1 report that that contains information about 20 different projects.

Describe the solution you'd like

A way to pass a list of project ids to be scanned using some flag or another. I.g. allow the --project-id flag to accept a list of projects

Describe alternatives you've considered

Giving all the necesasry permissions to a SA in specific projects instead of defining it on the org level. This alternative could work for a small number of projects in an organization, but if you'd want to scan 100 out of 1000, this is not feasiable.

Additional context

There was a similar issue that was borught up some years ago, but in the end, the changes to the scanning logic do not provide a solution for this.

Please correct me if I'm wrong, but I don't see a way to scan a list of specific projects, under different folders, using a single service account, without granting the SA permissions on each project individually (for large amount of projects, unsustaiable).

@Spiroman Spiroman added the enhancement New feature or request label Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant