nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

includePath filter

Natasha

Hi All,

We have a deployment configuration file where we have some "includePath" filters defined only at source and doDeletes="on", does that mean that will it delete all the folders/files on target which have not been inlcuded in the include filter?

My understanding is that it shouldn't delete the files apart from those specified in includes filter. Please confirm.
Thanks,
Natasha.
TS 6.7.1 Solaris 10, OD 6.1

Find more posts tagged with

Comments

Adam Stoller

Hi All,

We have a deployment configuration file where we have some "includePath" filters defined only at source and doDeletes="on", does that mean that will it delete all the folders/files on target which have not been inlcuded in the include filter?

My understanding is that it shouldn't delete the files apart from those specified in includes filter. Please confirm.
Thanks,
Natasha.
TS 6.7.1 Solaris 10, OD 6.1

It's been a while since I've done filtered deployments - even longer since doing an includeFilter deployment.

Your best bet is to create a simple scenario to test it out it - make a copy of the test.xml deployment configuration file (e.g.: test_remote.xml) that deploys to a remote server's ODHOME/tmp directory. Go to that directory and place a number of files with different extensions and two subdirectories, also with a number of files with different extensions - then modify the test_remote.xml to have two include filters: one should specify only files of a certain extension, the other should specify one of the two subdirectories.

Run the deployment in simulated mode first and check the logs.
Then run the deployment for real and check the results on the receiver.

If all looks good - you should be able to do what you want with your real deployment configuration file, otherwise ... (I seem to recall that there was some combination of filters that you weren't able to use in combination - but that could be mistaken, or it could have been fixed in newer releases)

I'd recommend this empirical method of verification regardless of what someone else posts here - it's generally easy to setup, and will give you a definitive answer.

Firenze

My expectation would be that anything found in the include path on the source side will need to found on the target side or it will be deleted. You can also set up your scenario and run a simulate deployment to test your results.

Adam Stoller

My expectation would be that anything found in the include path on the source side will need to found on the target side or it will be deleted. You can also set up your scenario and run a simulate deployment to test your results.

Your first statement is, I believe, incorrect. Anything found in the include path on the source side that is not found on the target side would be deployed, not deleted.

Your second statement is essentially what I already proposed, in more detail.

Firenze

Agreed. Thanks for the catch.

What I was trying to convey was that if there are files on the target side that are not also on the source side, then I would expect them to be deleted when doDeletes is on. My inferrence of the original post was that there may have been an expectation that doDeletes would ignore files on the target that were not in the include. For directory comparisons deployments, the whole directory and its contents is taken into account.