[
https://issues.apache.org/jira/browse/SLING-9556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172296#comment-17172296
]
Oliver Lietz commented on SLING-9556:
-------------------------------------
[~npeltier], Do not underrate the "just more efficient".
In a managed services setup we have several people (including externals from
system integrators) with read access to large (all) parts of the repo
(including pipes) but only the admin (CSE) should be able to run the pipes.
Removing read access on the pipes is therefore not an option and we can also
not remove the POST access. The "permission resources" is an indirection but
doesn't sound too bad... [~bdelacretaz], Can you elaborate on dev@?
> add pipes execution through a simple text POST
> ----------------------------------------------
>
> Key: SLING-9556
> URL: https://issues.apache.org/jira/browse/SLING-9556
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Pipes 4.0.0
> Reporter: Nicolas Peltier
> Assignee: Nicolas Peltier
> Priority: Major
> Fix For: Pipes 4.0.0
>
>
> problem with configuration of most pipes is JCR serialization is difficult to
> read/maintain (basic XML maintenance issue).
> Since it can be executed through gogo commands, the pipe could also simply be
> some piped command in a text file that would be posted to the plumber, using
> same pipebuilder functionality (see
> https://github.com/apache/sling-org-apache-sling-pipes/blob/master/src/main/java/org/apache/sling/pipes/internal/GogoCommands.java#L81)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
