Choose Delete action per Metadata Type for CI jobs
In the past we had troubles deploying reports via CI, they were not showing/deploying, the workaround was to enable the filter to include all reports. This works to solve that, but now I am looking at including more into the repo and start using delete actions in the CI jobs as well. The downside is that because we have to have all reports in the filter, the CI job will delete reports created by users in non-private folders. A freedom we want to give certain users in Production.
What would be an epic enhancement (and solve this challenge) is if you could decide to do delete actions per metadata type. Then I'd configure delete actions for everything except Reports and List Views for example.
Jan van Os
shared this idea
-
Pablo
commented
-
Kris Goncalves
commented
definitely a great idea. With source control, we want the flexibility to deploy new reports/dashboards/list views we may build but don't have all of that metadata in source control as it's changed by end users in production as well.
-
Eric Kintzer commented
worthwhile idea; could also include object translations
-
Martin Novacek
commented
Specially needed if you push a change in the repository and this will be interpreted as a deletion and the CI job deploy only changes and new things.
-
Pablo
commented
As of now, if you have deletions enabled in a CI job, everything is deleted. It would be great to be able to specify which metadata types you want to include in the deletions since normally you won't need to delete all differences. This would be specially helpful to remove Apex classes and its permissions from profiles.