Crates.io ops bot features

[carols10cents]

This is a list of features that we need a bot to have in order to empower more folks to help with crates.io ops without needing full access to the heroku app.

This should probably be moved to individual issues on a new repo once we come to a consensus on which of these we do or do not need.

• discord bot
• listens in #crates-io
• configurable allow list of which commands are allowed to be run by which people
• The bot should let the allowed people run particular Heroku commands: restart, ps:scale, revert, config:set, and config:get
  • config set/get should have another allow list for which vars are allowed
  • The implementation should shell out to the heroku CLI with credentials that do have full access
• Other crates.io specific commands:
  • backdate crate X (so it doesn't appear on the new crates list)
  • hide the new crates display for Y hours
  • hide crate X from any browsing and only show it for direct URL accesses

Please feel free to edit this if you have permissions and comment if you don't and you have changes.

[ashleygwilliams]

hi! so my vision for the bots is this:

the bots are a way for people without full heroku perms to do some lowkey operations on the site if/when folks with full perms aren't available.

i think the first feature should just be to restart the service.

after that, perhaps hiding a crate.

anything else is probably a bit more complicated and i'd like to see how this goes first!

[pietroalbini]

Since more and more Rust services are using Heroku (like the new website, and possibly docs.rs in the future), we should probably make this not tied to crates.io.