Skip to content
This repository was archived by the owner on Aug 18, 2020. It is now read-only.

REST Input/Output & Http Output #85

Closed
sebinside opened this issue Jul 11, 2019 · 4 comments
Closed

REST Input/Output & Http Output #85

sebinside opened this issue Jul 11, 2019 · 4 comments
Labels
api Requires api changes enhancement New feature or request io Relies on a connector / input / output / parameter major Needs a major platform / framework / build environment rework

Comments

@sebinside
Copy link
Member

Description

There should be an easy way to registern REST-like API interfaces for plugins in a separate scope then the global API. Connector support and input should be declared. A http output is another idea.

References

This issue replaces #81, which was not specific enough.

@sebinside sebinside added enhancement New feature or request major Needs a major platform / framework / build environment rework io Relies on a connector / input / output / parameter api Requires api changes labels Jul 11, 2019
@sebinside sebinside added this to the pre-alpha 3 milestone Jul 11, 2019
@sebinside sebinside self-assigned this Jul 11, 2019
@sebinside sebinside removed their assignment Jul 14, 2019
@strifel
Copy link
Contributor

strifel commented Jul 21, 2019

I like the Idea of an http connector.
This could be a connector which gets a regex scheme of a url the plugin can access, to not allow full internet access?

@J0B10
Copy link
Member

J0B10 commented Jul 21, 2019

Or just a list of base urls.
I think its better to make controlling such security relevant stuff as easy as possible.

@sebinside
Copy link
Member Author

Why controlling it at all? Who should specify, which web requests are OK? I don't see the clear vulnerability of get and post requests, when we have code execution disabled.

@sebinside sebinside modified the milestones: pre-alpha 3, alpha 1 Aug 7, 2019
@sebinside
Copy link
Member Author

As mentioned in #143, could be a super type for http communication, e.g. for OLA #142 or AHK #140.

This was referenced Dec 3, 2019
@sebinside sebinside changed the title REST Input & Http Output REST Input/Output & Http Output Dec 3, 2019
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
api Requires api changes enhancement New feature or request io Relies on a connector / input / output / parameter major Needs a major platform / framework / build environment rework
Projects
None yet
Development

No branches or pull requests

3 participants