Thank you both for the ideas. At this point we are thinking of a larger changes (more than just property mappings or resource type changes), so Daniel's approach sounds like a better fit.
When you say "pull it down" do you mean via the REST Api? If not, what other way to export the data is there? Same question for "reloading"... is this a reload using the REST api's "import" operation? On Wed, Jun 10, 2020 at 9:03 AM Daniel Klco <dk...@apache.org> wrote: > I agree with Nicolas' approach, however it depends on the scale you're > attempting to make changes. > > If it's fairly straight forward such as resourceType/a => resourceType/b or > property mapping, Sling Pipes is a great solution. If you need to do a > *lot* of > changes to the structure if your content, you may be better to pull it > down, transform it offline and reload. > > On Wed, Jun 10, 2020 at 2:51 AM Nicolas Peltier <npelt...@apache.org> > wrote: > > > Hi Carlos, > > > > one approach (not saying it's the best, i'm the main maintainer of them) > is > > to use a handful of sling pipes [0] and script to kick them off, or as > > package hooks. > > > > Nicolas > > > > [0] https://sling.apache.org/documentation/bundles/sling-pipes.html > > > > Le mar. 9 juin 2020 à 23:55, Carlos Munoz <camu...@redhat.com> a écrit : > > > > > Hi Sling devs, I was wondering what the best approach would be to take > an > > > exisiting repository and making changes to the content structure in a > > safe > > > and repeatable way. > > > > > > Thanks in advance! > > > > > >
