-
Notifications
You must be signed in to change notification settings - Fork 69
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
feat: trigger name limit #1080
feat: trigger name limit #1080
Conversation
/build |
// LimitsConfig contains limits for some entities. | ||
type LimitsConfig struct { | ||
// Trigger contains limits for triggers. | ||
Trigger TriggerLimits |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
а зачем такая вложенность? будут еще какие-то лимиты на триггер?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Мы с Олегом эту штуку обсудили, решили оставить так. Вот аргументы за:
- вполне можно ожидать появления других лимитов как для триггера (например, на число тегов у триггера, на длину описания и т.п.), так и для других сущностей.
- ожидается, что эта структура будет создана и заполнена один раз, положена в контекст запросов, а потом она будет нужна для получения их неё значений
/build |
Build and push Docker images with tag: 2024-10-15.6541929 |
1 similar comment
Build and push Docker images with tag: 2024-10-15.6541929 |
PR Summary
Before this PR there was no limit to trigger name. This can lead to problems with alert delivering.
This PR adds configurable limit for trigger name. It is highly recommended not to increase it.