Skip to content

Draft: Add a feature flag to selectively disable npm_allow_packages_in_multiple_projects

Radamanthus Batnag requested to merge 463214-add-feature-flag-for-selective-disable into master

🌱 Context

While incrementally enabling the feature flag npm_allow_packages_in_multiple_projects, we encountered HTTP 500s on a customer namespace with a large number of packages (internal).

To enable us to rollout this feature flag, we can introduce a new override feature flag, npm_allow_packages_in_multiple_projects_override. This will let us selectively disable npm_allow_packages_in_multiple_projects for those namespaces with large numbers of packages.

What does this MR do and why?

This MR introduces the npm_allow_packages_in_multiple_projects_override feature flag to allow selective disabling of npm_allow_packages_in_multiple_projects for namespaces with large number of packages.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

No UI changes 🌈

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Related to #463214 (closed)

Edited by Radamanthus Batnag

Merge request reports