[jira] [Closed] (SLING-10846) Sling Pipes to write metadata on modified resources

["Nicolas Peltier (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Peltier closed SLING-10846.
-----------------------------------

> 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)