crowdsecurity
Ease the upgrade journey
What would you like to be added?
Currently, when a user upgrades its SaaS plan, he needs to take several steps to take advantage of it:
- enable
console_managementviacscli - restart crowdsec
We want to ensure the user doesn't have to take any extra steps to use it. Once the user upgrades its organization, CrowdSec SE should be made aware and enable console_management unless the user explicitly opted out.
We need also to update the "text" of console_management to be more explicit: it also allows you to get real-time blocklists and allowlists.
Why is this needed?
Make user's life easier.
@buixor: Thanks for opening an issue, it is currently awaiting triage.
In the meantime, you can:
- Check Crowdsec Documentation to see if your issue can be self resolved.
- You can also join our Discord.
- Check Releases to make sure your agent is on the latest version.
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
@buixor: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.
/kind feature/kind enhancement/kind refactoring/kind bug/kind packaging
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.
