You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Honwai Wong (JIRA)" <ji...@apache.org> on 2017/12/14 16:21:00 UTC
[jira] [Created] (SLING-7314) Dry run not working
Honwai Wong created SLING-7314:
----------------------------------
Summary: Dry run not working
Key: SLING-7314
URL: https://issues.apache.org/jira/browse/SLING-7314
Project: Sling
Issue Type: Bug
Components: Extensions
Affects Versions: pipes 1.1.0
Reporter: Honwai Wong
I worked with [~npeltier] to define a pipe to perform content migration, see below for an example of this pipe:
{code}
def plumber = getService("org.apache.sling.pipes.Plumber");
plumber.newPipe(resourceResolver)
.echo('/content/foo/bar').name('startPath')
.mv('${path.startPath.replace("/bar", "/xyz")}')
.parent().name('parentContent')
.mkdir('${path.parentContent}/bar').with('nodeType', 'nt:unstructured').name('targetResource')
.write('sling:resourceType', 'test/components/somecomponent')
.echo('${path.parentContent}/xyz')
.mv('${path.targetResource}/xyz')
.runWith("dryRun", "true");
{code}
However, the {{dryRun}} argument is not taken into account, the changes are actually persisted in the repository.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)