Worker platform and key improvements

[collectoss-issue-migrator]

Note

Migrated from augurlabs/augur#3087
Originally opened by @Ulincsys on 2025-03-22

---

Update the platform table with the following goals:

• Add user-facing "Pretty name" column for identifying the platform to the user
• Add "enabled" column to indicate whether or not collection should run for the given platform
  • The actual functionality of enabling or disabling a platform can be done later

Update the worker oauth table with the following goals:

• Add "platform features" column for storing key pseudo-platforms (IE: the different request limits for each key type).
  • EG: rest and graphql

Stop storing keys in the config table:

• Ensure that all references to the keys stored in the config are removed, and replaced with the KeyClient and KeyPublisher
• On install, keys should be stored in the oauth table by default

[collectoss-issue-migrator]

Note

Migrated comment from original
Originally posted by @KhanRayyan3622 on 2025-03-28

---

Hi! I'd like to work on this issue. I’ll start by adding the pretty_name and enabled columns to the platform table and can follow up with the OAuth table and key migration. Let me know if there’s anything I should keep in mind while making these changes!

[collectoss-issue-migrator]

Note

Migrated comment from original
Originally posted by @guptapratykshh on 2026-01-16

---

i am working on it

[MoralCode]

#293 basically "refactors" this issue to use a new paradigm that i think is a much better model for the future. Closing as superseded