Skip to content

ratelimits: Use more compact overrides YAML representation #7197

@beautifulentropy

Description

@beautifulentropy

The overrides YAML file is formatted identically to the defaults file:

// Tier 1
enumStr:Id1:
  burst: 10
  count: 10
  period: 10s
enumStr:Id2:
  burst: 10
  count: 10
  period: 10s

// Tier 2
enumStr:Id3:
  burst: 20
  count: 20
  period: 10s

This leads to a lot of repeated limit data. Instead, we should format them like so:

// Tier 1
- enumStr:
    burst: 10
    count: 10
    period: 10s
    ids:
      - Id1
      - Id2
 
// Tier 2
- enumStr:
    burst: 20
    count: 20
    period: 10s
    ids:
      - Id3

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions