No-op SetApiRateLimitsToZero migration

Abdul Wadoodrequested to merge
545306-no-op-set-api-rate-limits-to-zero-migration into master

What does this MR do and why?

This MR converts the SetApiRateLimitsToZero migration into a no-op migration.

In !189906 (merged), we introduced a migration to set the rate limits to 0 for existing self-managed instances to avoid disrupting their workflow. However, for new SM installations, we want them to receive the proper rate limits instead of having them set to zero.

By making this migration a no-op, new self-managed instances will get the default rate limits configured, while existing instances that already ran this migration remain unaffected.

References

Closes #545306 (closed) Related to #461316 (comment 2456342461)

How to set up and validate locally

  1. Run bin/rails db:migrate to ensure the migration runs without errors
  2. Verify that the migration does not modify any rate limits in the application settings
  3. Run the updated spec: bundle exec rspec spec/migrations/20250501083748_set_api_rate_limits_to_zero_spec.rb

MR acceptance checklist

This MR has been evaluated against the MR acceptance checklist.

  • Migration updated to milestone 18.3
  • Migration logic converted to no-op
  • Spec file updated to test no-op behavior
  • Existing instances remain unaffected (migration already ran)
  • New instances will receive proper rate limits

Merge request reports