Removal of objects not in source when only selected folder is published

[TybulOnAzure]

Hi @NowinskiK

I'm just starting with this great tool and I'm a bit confused about the following case:

1. I have an ADF instance inside which I created a SomeArea folder with two pipelines:
   
2. I deployed it to live instance using selective approach (remaining options are set to defaults):

$selectedObjects = $adf.GetObjectsByFolderName('SomeArea')
$opt.DeleteNotInSource = $true

3. Everything works fine so far and those two pipelines have been successfully deployed.
4. Then I removed pipeline2 from ADF and executed the CI/CD pipeline again.
5. It detected that only pipeline1 is included in my SomeArea folder:
   
6. ... and deleted one object:
   

However, both pipelines still exist in the live ADF instance as nothing was actually deleted. So my questions are:

1. What should happen in the described case? Should pipeline2 be removed from live ADF?
2. What object was marked as removed in logs?

Basically, I'm trying to think about a scenario, in which multiple teams work on the same ADF instance so they use their own CI/CD pipelines with selective approach. But what if one team would like to remove one of its previously deployed objects - how to achieve this without affecting other teams?

Additional notes: I used 1.7.000 version of ADF Tools.

Piotr Tybulewicz

[NowinskiK]

Hi Piotr. Thanks for using the tool and raising a question.
Based on what you have described - yes, pipeline2 should be deleted.

However, it's easier way to define deployment using logical folders.
Use wildcard pattern like this: *.*@SomeArea.
More examples: Pattern wildcard

Do you know what object has been deleted in step 6?
If not - enable diagnostic/debug mode (DevOps pipeline) and you should see more details.

The scenario you're considering is vital & real.
DeleteNotInSource flag will not drop target objects excluded from the deployment. It's purely excluded from deployment, so should not be touch during the process at all. When you're not sure what will happen with combinations of options - you can check the action matrix presented in section Selective Deployment.

Hope this help. If not - feel free to reach me out.

[TybulOnAzure]

Hi Kamil.

Thanks for the hint to enable diagnostic mode - everything is clear now:

So the pipeline2 was not deleted due to DoNotDeleteExcludedObjects flag set to true. It also means that the summary of the Deleting step is a bit misleading as it doesn't show the number of objects that were actually removed from ADF service, but the number that was considered for removal.

---

Anyway, to remove just pipeline2 I used such approach:

1. I explicitly added it to the list of included objects:
   
   as apparently method to get objects by folder name was not enough as this pipeline doesn't exist in the source code anymore.
2. Then, during the deployment, the pipeline has been removed:
   

Comparison of options:

1. When including objects by folder name, only pipeline1 was included:
   

2. When including objects explicitly by object name, pipeline2 was also included and therefore was later removed: