Feature request: use modern permissions

[petrmanek]

GPIO Control is a really neat and useful plugin, however using it with multiple users and varying access levels seems to be cumbersome. Case in point, in the current version the plugin effectively requires that all users to be in the "Operator" group in order to control GPIO.

This is because:

• The GPIO Control plugin requires old-style "USER" permission in order to permit API calls.
• The "USER" and "ADMIN" permissions were deprecated and linked to membership in the "Operator" and "Admin" groups respectively. Their future use is discouraged.
• There is now a mechanism for registering and controlling custom plugin-specific permissions, which should be used for this purpose.

For this reason, all users in the "Operator" group have the "USER" permission necessary to use GPIO Control. However, in my application users (and groups) are populated from LDAP and their permissions are inherited -- unfortunately this has no effect, and neither such user is allowed to perform GPIO Control API calls on the grounds of insufficient permissions.

Feature request: I would like to propose that this plugin adopts the new way of declaring and controlling granular permissions. This would solve the problem by allowing arbitrary groups, possibly different from "Operator", to be allowed API access to GPIO Control.

[petrmanek]

@catgiggle Bumping this after nearly two months. Could I please get any response from the maintainer? If nothing else, would anybody be interested in merging this if I implemented it?

[petrmanek]

@catgiggle 9 months later, here we are. Is this repository officially dead?