Usage Quotas and Statistics are Tracked in Configuration

Problem/Motivation

It appears that usage quotas are stored as configuration. This can result in deployment pipelines breaking as Acquia BLT and other deployment tools might detect an unmatched configuration change, causing the pipeline to break until the configuration change is addresssed.

This does not follow Drupal best practices as the state of these usage quotas do not belong in configuration at all. Instead they should be tracked using Drupal's State API → .

Steps to reproduce

1. Install and configure MiniOrange 2FA
2. Export the configs to disk where config sync can see it
3. Use MiniOrange 2FA to authenticate several times
4. Go to /admin/config/development/configuration and observe that Drupal indicates that the configuration is out of sync.

Proposed resolution

Update the module's code such that these usage quotas are tracked using Drupal's State API → .

Remaining tasks

• Make the Appropriate Code Changes
• Test the Code
• Commit to Dev Branch
• Create a release

User interface changes

None

API changes

Usage quotas are tracked using Drupal's State API →

Data model changes

None