Ampersand breaks replication agent transport_uri

[sambanks]

Hi Guys

The module has been working great for me (and saving huge amounts of time thanks!) so far, however I have found one minor issue and was wondering if it was something you had come across.

It works if I have a rep queue that looks like the following:

adobe_em6::instance::replication_queues:
publish:
transport_uri: 'http://ci-pub1.foobar.com:4503/bin/receive?sling:authRequestLogin=1'
serialization_type: 'binary-less'

But if I use the ampersand for binary less (s3 datastore) puppet detects the change during the agent run, and installs a new package with the correct uri, however it's not updated in AEM.

adobe_em6::instance::replication_queues:
publish:
transport_uri: 'http://cii-pub1.foobar.com:4503/bin/receive?sling:authRequestLogin=1&binaryless=true'
serialization_type: 'binary-less'

I know it's possibly more of an AEM problem, but thought there may be a way of escaping or dealing with it in the module that you had come across?
Cheers
Sam

[jbornemann]

Hey Sam!

Sorry for the issues, but thanks for reporting!

I haven't seen this issue before, but then again we primarily only deal with Durbo serilization. You said that the new package is indeed installed when you make the ampersand change?

One way to be sure is to check under /<aem_folder>/queue_tmp. This is the replication queue staging area where Puppet builds the replication packages before install.

[sambanks]

Thanks for the info, yeah it does get created. I suspect it's a bug with the package manager, as you can manually remove the query string from the package and it works. I've logged a ticket in daycare and will update here.

Cheers