[jira] [Updated] (SLING-10846) Sling Pipes to write metadata on modified resources
[
https://issues.apache.org/jira/browse/SLING-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-10846:
Fix Version/s: Pipes 4.3.0
(was: Pipes 4.3.2)
> Sling Pipes to write metadata on modified resources
> ---
>
> Key: SLING-10846
> URL: https://issues.apache.org/jira/browse/SLING-10846
> Project: Sling
> Issue Type: Improvement
> Components: pipes
>Reporter: Mariia Lukianets
>Assignee: Nicolas Peltier
>Priority: Minor
> Fix For: Pipes 4.3.0
>
>
> h4. Background
> Sling Pipes modify content without leaving a trace in the repository.
> Developers should have the ability to mark resources modified by the Sling
> Pipe. While modifying the resource, the 'Write' Sling pipe could also set
> metadata info indicating the time of modification and the author of the
> change.
> *Example*: pipe 'enable-foo' sets the property foo=true on nodeA.
> without metadata:
> nodeA
> foo=true
> with metadata:
> nodeA
> foo = true
> jcr:lastModified = 2021-08-09T11:06:56.753+02:00
> jcr:lastModifiedBy = sling-pipe-enable-foo
> h4.
> h4. Suggestion
> To add a 'metadata' flag to content modification pipes. When set to true, the
> pipe will set 2 properties on each modified resource:
> * 'jcr:lastModified' - current server's DateTime.
> * 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name}'
> By default, the metadata flag is set to false and will do nothing.
> Q1. should we make 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name} on behalf
> of ${user}'?
> Q2. what other pipes to adapt
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-10846) Sling Pipes to write metadata on modified resources
[
https://issues.apache.org/jira/browse/SLING-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-10846:
Component/s: Extensions
> Sling Pipes to write metadata on modified resources
> ---
>
> Key: SLING-10846
> URL: https://issues.apache.org/jira/browse/SLING-10846
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
>Reporter: Mariia Lukianets
>Priority: Minor
> Fix For: Pipes 4.3.0
>
>
> h4. Background
> Sling Pipes modify content without leaving a trace in the repository.
> Developers should have the ability to mark resources modified by the Sling
> Pipe. While modifying the resource, the 'Write' Sling pipe could also set
> metadata info indicating the time of modification and the author of the
> change.
> *Example*: pipe 'enable-foo' sets the property foo=true on nodeA.
> without metadata:
> nodeA
> foo=true
> with metadata:
> nodeA
> foo = true
> jcr:lastModified = 2021-08-09T11:06:56.753+02:00
> jcr:lastModifiedBy = sling-pipe-enable-foo
> h4.
> h4. Suggestion
> To add a 'metadata' flag to content modification pipes. When set to true, the
> pipe will set 2 properties on each modified resource:
> * 'jcr:lastModified' - current server's DateTime.
> * 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name}'
> By default, the metadata flag is set to false and will do nothing.
> Q1. should we make 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name} on behalf
> of ${user}'?
> Q2. what other pipes to adapt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-10846) Sling Pipes to write metadata on modified resources
[
https://issues.apache.org/jira/browse/SLING-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-10846:
Component/s: (was: Extensions)
pipes
> Sling Pipes to write metadata on modified resources
> ---
>
> Key: SLING-10846
> URL: https://issues.apache.org/jira/browse/SLING-10846
> Project: Sling
> Issue Type: Improvement
> Components: pipes
>Reporter: Mariia Lukianets
>Priority: Minor
> Fix For: Pipes 4.3.0
>
>
> h4. Background
> Sling Pipes modify content without leaving a trace in the repository.
> Developers should have the ability to mark resources modified by the Sling
> Pipe. While modifying the resource, the 'Write' Sling pipe could also set
> metadata info indicating the time of modification and the author of the
> change.
> *Example*: pipe 'enable-foo' sets the property foo=true on nodeA.
> without metadata:
> nodeA
> foo=true
> with metadata:
> nodeA
> foo = true
> jcr:lastModified = 2021-08-09T11:06:56.753+02:00
> jcr:lastModifiedBy = sling-pipe-enable-foo
> h4.
> h4. Suggestion
> To add a 'metadata' flag to content modification pipes. When set to true, the
> pipe will set 2 properties on each modified resource:
> * 'jcr:lastModified' - current server's DateTime.
> * 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name}'
> By default, the metadata flag is set to false and will do nothing.
> Q1. should we make 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name} on behalf
> of ${user}'?
> Q2. what other pipes to adapt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-10846) Sling Pipes to write metadata on modified resources
[
https://issues.apache.org/jira/browse/SLING-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-10846:
Fix Version/s: Pipes 4.3.0
> Sling Pipes to write metadata on modified resources
> ---
>
> Key: SLING-10846
> URL: https://issues.apache.org/jira/browse/SLING-10846
> Project: Sling
> Issue Type: Improvement
>Reporter: Mariia Lukianets
>Priority: Minor
> Fix For: Pipes 4.3.0
>
>
> h4. Background
> Sling Pipes modify content without leaving a trace in the repository.
> Developers should have the ability to mark resources modified by the Sling
> Pipe. While modifying the resource, the 'Write' Sling pipe could also set
> metadata info indicating the time of modification and the author of the
> change.
> *Example*: pipe 'enable-foo' sets the property foo=true on nodeA.
> without metadata:
> nodeA
> foo=true
> with metadata:
> nodeA
> foo = true
> jcr:lastModified = 2021-08-09T11:06:56.753+02:00
> jcr:lastModifiedBy = sling-pipe-enable-foo
> h4.
> h4. Suggestion
> To add a 'metadata' flag to content modification pipes. When set to true, the
> pipe will set 2 properties on each modified resource:
> * 'jcr:lastModified' - current server's DateTime.
> * 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name}'
> By default, the metadata flag is set to false and will do nothing.
> Q1. should we make 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name} on behalf
> of ${user}'?
> Q2. what other pipes to adapt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-10846) Sling Pipes to write metadata on modified resources
[
https://issues.apache.org/jira/browse/SLING-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariia Lukianets updated SLING-10846:
-
Description:
h4. Background
Sling Pipes modify content without leaving a trace in the repository.
Developers should have the ability to mark resources modified by the Sling
Pipe. While modifying the resource, the 'Write' Sling pipe could also set
metadata info indicating the time of modification and the author of the change.
*Example*: pipe 'enable-foo' sets the property foo=true on nodeA.
without metadata:
nodeA
foo=true
with metadata:
nodeA
foo = true
jcr:lastModified = 2021-08-09T11:06:56.753+02:00
jcr:lastModifiedBy = sling-pipe-enable-foo
h4.
h4. Suggestion
To add a 'metadata' flag to content modification pipes. When set to true, the
pipe will set 2 properties on each modified resource:
* 'jcr:lastModified' - current server's DateTime.
* 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name}'
By default, the metadata flag is set to false and will do nothing.
Q1. should we make 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name} on behalf of
${user}'?
Q2. what other pipes to adapt
was:
h4. Background
Sling Pipes modify content without leaving a trace in the repository.
Developers should have the ability to mark resources modified by the Sling
Pipe. While modifying the resource, 'Write' Sling pipe could also set a
metadata info indicating the time of modification and the author of the change.
*Example*: pipe 'enable-foo' sets the property foo=true on nodeA.
without metadata:
nodeA
foo=true
with metadata:
nodeA
foo = true
jcr:lastModified = 2021-08-09T11:06:56.753+02:00
jcr:lastModifiedBy = sling-pipe-enable-foo
h4.
Suggestion
To add a 'metadata' flag to the write pipe. When set to true, write pipe will
set 2 properties on each modified resource:* 'jcr:lastModified' - current
server's datetime.* 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name}'
By default, the metadata flag is set to false and will do nothing.
Q1. should we make 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name} on behalf of
${user}'?
Q2. what other pipes to adapt
> Sling Pipes to write metadata on modified resources
> ---
>
> Key: SLING-10846
> URL: https://issues.apache.org/jira/browse/SLING-10846
> Project: Sling
> Issue Type: Improvement
>Reporter: Mariia Lukianets
>Priority: Minor
>
> h4. Background
> Sling Pipes modify content without leaving a trace in the repository.
> Developers should have the ability to mark resources modified by the Sling
> Pipe. While modifying the resource, the 'Write' Sling pipe could also set
> metadata info indicating the time of modification and the author of the
> change.
> *Example*: pipe 'enable-foo' sets the property foo=true on nodeA.
> without metadata:
> nodeA
> foo=true
> with metadata:
> nodeA
> foo = true
> jcr:lastModified = 2021-08-09T11:06:56.753+02:00
> jcr:lastModifiedBy = sling-pipe-enable-foo
> h4.
> h4. Suggestion
> To add a 'metadata' flag to content modification pipes. When set to true, the
> pipe will set 2 properties on each modified resource:
> * 'jcr:lastModified' - current server's DateTime.
> * 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name}'
> By default, the metadata flag is set to false and will do nothing.
> Q1. should we make 'jcr:lastModifiedBy' - 'sling-pipe-${pipe_name} on behalf
> of ${user}'?
> Q2. what other pipes to adapt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
