I need to have Conan packages with channel release (e.g. unity/2.4.3-1@peter/release which ends up in the folder hierarchy peter/unity/2.4.3-1/release/...) protected from being modified or deleted. Therefore i configured the following permission targets:
Delete/Overwrite for Include Pattern ** and Exclude Pattern */*/*/release/**
Deploy/Cache for Include Pattern */*/*/release/** only
This works well except that it is still possible to delete all packages including those with channel release in the UI by simply deleting one of the the parent folders, so one of 2.4.3-1, unity or peter in this example. Apparently the delete permissions of a sub-folder are not considered when determining the delete permissions of a folder. This renders the permission target patterns useless for such cases.
Of course it would be possible to use an additional repository for the release packages with Deploy/Cache permissions only but this leads to administrative effort and user errors.