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

Feature request for Handling Multiple Plugins #327

Closed
sumitra19jha opened this issue Jul 17, 2021 · 1 comment · Fixed by #333
Closed

Feature request for Handling Multiple Plugins #327

sumitra19jha opened this issue Jul 17, 2021 · 1 comment · Fixed by #333
Assignees

Comments

@sumitra19jha
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The feature is related to the idea of giving users the capability to add to use multiple plugins

Describe the solution you'd like
To update the API's and create the necessary schema modification

Describe alternatives you've considered
Use plugin as a part of the environment variable

Approach to be followed (optional)
Performs update by adding the required data model, create query and mutation related to it.

Additional context
This is a request made by Reetik

@github-actions github-actions bot added the unapproved Unapproved for Pull Request label Jul 17, 2021
@CyberWake
Copy link

Requirement a plugin table in database which stores configuration data of each organisation for all the plugins used in talawa-api.
Schema for a single plugin table object would we like:

{  id(org id)
   razorpayPlugin(RazorpaySchemma)
   plugin1Name(Schema for plugin 1)
   plugin2Name(Schema for plugin 2)
  ...
  ...
   all other plugins
}

RazorPay Schema:

{
   razorPayKey(id field from razorpay)
}

Mutation access permission:
super admin can set an environment variable to give rights to org admins to get donations keys set up.
If org admins don't have this right then plugin table should store the data for universal plugin configuration with any unique id.

Query Access:
Any user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants