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

Stop All Scans KillSwitch #1270

Closed
1 task done
tHeStRyNg opened this issue May 28, 2024 · 3 comments · Fixed by #1321
Closed
1 task done

Stop All Scans KillSwitch #1270

tHeStRyNg opened this issue May 28, 2024 · 3 comments · Fixed by #1321

Comments

@tHeStRyNg
Copy link

Is there an existing feature or issue for this?

  • I have searched the existing issues

Expected feature

Would be interesting to have a kill switch in which in large asset scannings, we would be able to stop all scans on one click or by organization if defined as at the moment if we have 200 assets we have to go one by one to stop them which isnt useful.

Alternative solutions

No response

Anything else?

No response

Copy link
Contributor

👋 Hi @tHeStRyNg,
Issues is only for reporting a bug/feature request. Please read documentation before raising an issue https://rengine.wiki
For very limited support, questions, and discussions, please join reNgine Discord channel: https://discord.gg/azv6fzhNCE
Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.

@yogeshojha yogeshojha self-assigned this Jul 22, 2024
@yogeshojha yogeshojha linked a pull request Jul 22, 2024 that will close this issue
@yogeshojha
Copy link
Owner

@tHeStRyNg Thank you for the feature request.

This has been added and will be available in next release.

#1321

yogeshojha added a commit that referenced this issue Jul 31, 2024
@yogeshojha
Copy link
Owner

This is released in reNgine 2.2.0, checkout: What's new in 2.2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants