Inconsistent `pipeline_triggers` limit across plans
Problem
When looking at the existing plan limits I noticed that pipeline_triggers
is not set for some plans. It looks like newly introduced plans in SaaS have it missing.
[ gprd ] production> PlanLimits.joins(:plan).pluck(:name, :pipeline_triggers)
=> [["early_adopter", 25000], ["bronze", 25000], ["silver", 25000], ["gold", 25000], ["free", 25000], ["default", 0], ["premium", 0], ["ultimate", 0], ["ultimate_trial", 0], ["premium_trial", 0], ["opensource", 0]]
This would allow projects to create unlimited pipeline triggers for those plans.
The limit is described here https://docs.gitlab.com/ee/administration/instance_limits.html#limit-the-number-of-pipeline-triggers
Solution
- Check if any project under that plan has more than
25,000
pipeline triggers. - If none, update the plan limit to
25000
using the existing migration helper method.
Edited by Fabio Pitino