This is cool, although what I
really wish for is a standardized configuration API that can be programmatically used to maintain this sort of thing.
We develop apps that depend on a handful of services like these. Each service has its own page for specifying API credentials and for various configuration options which must be entered manually through a GUI; it can't be declared through Puppet/Chef/etc.
Another pain point is that every service needs its own login, very few of them support 2FA, very few of them support team-oriented accounts (ie., where login is separate from the account, and access is delegated to the account; Mailgun and Digital Ocean, for example, lacks this, whereas Scout, Rollbar etc. don't), each has a completely proprietary health status page, etc.
I am hoping someone someday will invent a centralized app (preferably based on an open protocol so there can be multiple providers) for this kind of organizational access. Sort like OpenID, except it needs role-based permission levels.
We develop apps that depend on a handful of services like these. Each service has its own page for specifying API credentials and for various configuration options which must be entered manually through a GUI; it can't be declared through Puppet/Chef/etc.
Another pain point is that every service needs its own login, very few of them support 2FA, very few of them support team-oriented accounts (ie., where login is separate from the account, and access is delegated to the account; Mailgun and Digital Ocean, for example, lacks this, whereas Scout, Rollbar etc. don't), each has a completely proprietary health status page, etc.
I am hoping someone someday will invent a centralized app (preferably based on an open protocol so there can be multiple providers) for this kind of organizational access. Sort like OpenID, except it needs role-based permission levels.