-
Notifications
You must be signed in to change notification settings - Fork 308
Create small app to act as dynamic one-page dashboard for communicating service access #2220
Comments
@patcon Would https://enterprise.lastpass.com/ do what we need here? |
I've upgraded this to TeamX ★. I really need to delegate access to @patcon @bruceadams @pjf et al. so they can handle support and ops issues. I'm overwhelmed! |
Got a dead-simple version set up: Code here: Will be tracking issues in it's issue queue. I'm down to transfer to gittip org if that's better |
Transferred to gittip/access-dashboard! |
Awesome. :-) |
Closing this issue now that we have a new repo started. Let's reticket specific issues over there? |
Balanced apparently has an undocumented api that their dashboard uses to manage users, so I'll look into that later (and maybe submit a docs PR to them): (Added link to original post) |
As a replacement for http://building.gittip.com/appendices/access
This would seem to be a useful tool for an Open Company that wants to make it known who has access it what, without being slave to meticulous documentation.
Similar tools exist, but they're paid and proprietary, and intended to be read-write, rather than just read:
https://twitter.com/patconnolly/status/450738292468641792
The idea is that you would feed the app API keys as envvars, and apply more general config in a simple yaml file. The yaml file could also be used for configuring the services that don't offer the proper API access.
Would love to use this as an opportunity to use the camping microframework:
https://github.com/camping/camping
Services [WIP]
Even though many services can have dynamic access via API, it will make sense to configure most via YAML, and just add the code to make it dynamic as more people need access to those services, and it starts being in flux
The text was updated successfully, but these errors were encountered: