Can applyExtAttrs be used with regular comparison deployment

Johnny

The test didn't work out for me, but here's the question anyway...

Once and a while I need to sync content from production down to uat.
I was going to use the applyExtAttrs that comes with OD 6.x but it only works with TeamSite comparisons. The only way I could get this to work for my use was to do a full TeamSite comparison deployment (IE previousArea ="/default/main/EDITION/INITIAL"), but obviously that is too time consuming to do a full deployment each time. Am I able to do a directory (target vs source) comparison at all or do I need to revert back to the old getattr.ipl, setattr.ipl via DNR's?

BTW - when would it be useful for it to be a TeamSite comparision with applyExtAttrs used?

Thanks again

Adam Stoller

I believe the reason it only works with TeamSite based comparisons is because the notion of EAs is tied to using TeamSite areas for both source and target locations.

Clearly, it is possible to specify file system paths to TeamSite areas for both source and target locations, but (and this is a guess) it might be more confusing getting strange errors from a deployment that tried to do this when the source and/or target file system paths did *not* point to a TeamSite area.

BTW - when would it be useful for it to be a TeamSite comparision with applyExtAttrs used?

When all your deployments are done that way - i.e. if you always cut new editions before deploying to your receivers.

Frankly, although I understand the reasons for TeamSite deployments - I've tended to find that they're generally less useful and require more planning than file system comparisons or filelist deployments (e.g. you need to track the last successful edition deployed in order to ensure that all new content gets deployed in a subsequent deployment - you cannot always use the latest versus the previous [latest-1] edition).

However, all this being said - this is probably something worth filing a feature request for, as it may not be that difficult to do - and to provide useful diagnostic errors in cases where it fails...