Skip to content

[Feature Request] Enable/disable plugins through API #21

@NODeeJay

Description

@NODeeJay

Is your feature request related to a problem? Please describe.
No, it's a pure FR.

Describe the solution you'd like
As a user for the MCSS API I would like to be able to enable or disable plugins through the API. Furthermore, I would like to be able to query the details of existing plugins, regardless of them being enabled or disabled.

GET https://localhost:25560/api/v2/servers/e0ae4902-10ed-481f-aed0-fa1170ec779a/plugins shows me all details from plugins. The json is split into 2 objects, enabled and disabled containing the respective plugins (see additional context).

POST https://localhost:25560/api/v2/servers/e0ae4902-10ed-481f-aed0-fa1170ec779a/plugins/BackInPack "action": 1 to enable, and "action": 0 to disable

If the server is running the command to enable/disable plugins is throwing an error.

Describe alternatives you've considered
Calling a batch file from a remote system to rename the plugin to enable/disable it. Very unpractical.

Additional context
Since it's API there is not much wireframe I can provide.
and the structure of the API response is straight forward:

  • plugins
    • enabled
      • Name of enabled plugin 1
        • Description
        • Website
        • Authors
        • Location
        • Filesize
        • API version
        • Main
        • Dependencies
        • Soft Dependencies
      • Name of enabled plugin 1
    • disabled
      • Name of disabled plugin 1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions