Closed jbornemann closed 7 years ago
@jbornemann : Installing this package did not fix the error for me.. Moreover it has an unmet dependency as I am not using any SP
@viveksachdeva sorry, I uploaded a new one.
Grabbit-Deserialization-Firewall-Configuration-1.0.zip
Any idea how to upload a generic file to https://bintray.com/twcable/aem/Grabbit#files/dependencies?
Everything I read is about uploading packages
Nevermind, got it figured out. You have to attach all files to a specific existing package version.
This is interesting ... getting caught up now.
Should we have the config be -amended
? So that we don't overwrite incase the instance Grabbit getting installed to .. already has a config for the Deserialization service?
I think that way .. we can add only our stuff to the whitelist ...
Also, I didn't check thoroughly but do we need to update the filter.xml on grabbit so the /apps/grabbit/config/security
doesn't get inadvertently wiped out when Grabbit is installed / re-installed ?
Agree with both the points from @sagarsane .. /apps/grabbit/config/security
is getting wiped on on grabbit reinstall...
But on installing this package and running a sync from 6.2 -> 6.1 works fine..
Thanks guys. I didn't even think about filter.xml. I've updated the package, and the PR to accommodate.
-amended might work if we were dealing with just whitelist, but since blacklist is evaluated first, we have to remove those spring entries.
I am able to do content sync from 6.2 -> 6.1 with this package installed but when I uninstall grabbit, this deserialization config also goes away
Make sure you have the updated branch installed, and the updated package installed before you test the uninstall. Trying to uninstall when the old branch is already installed won't work.
@jbornemann : Yes I did install the latest package with the updated branch having
Sorry @viveksachdeva, I'm seeing what you are seeing now. Different behavior per install vs uninstall. I forgot how finicky working with the workspace filter is. I've got it down now. Promise :) Mind trying again?
No problem @jbornemann . I will try this one tomorrow..
FYI @viveksachdeva