Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Plugin config approach: support global settings and server-side community settings #71

Closed
gigxz opened this issue Jun 4, 2021 · 0 comments
Labels
enhancement New feature or request for metagov-core
Projects

Comments

@gigxz
Copy link
Collaborator

gigxz commented Jun 4, 2021

Currently plugins need to define config as a JSON schema on the model, and configs are all community-specific.
This issue is for:

  • Adding support for global (NOT community-specific) settings, like Slack Client ID. Possibly client-facing global configurations, too.
  • Support "private"(?) community-specific config, like the bot_token in the Slack. These settings should not be exposed in the client, they are configured automatically using oauth flow.
@gigxz gigxz added the enhancement New feature or request for metagov-core label Jun 4, 2021
@gigxz gigxz added this to 🦑. Backlog in Metagov via automation Jun 4, 2021
@gigxz gigxz closed this as completed Dec 3, 2021
Metagov automation moved this from 🦑. Backlog to ✅ Done Dec 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request for metagov-core
Projects
Metagov
✅ Done
Development

No branches or pull requests

1 participant