Option to delete XML config transforms after applying

[nblumhardt]

Via http://help.octopusdeploy.com/discussions/questions/243-deleting-config-transformation-files-after-deploy

Lingering .config files cause issues for some applications.

[PaulStovell]

Given this file system:

Web.config
Web.Dev.config
Web.Prod.config
Web.Release.config

Assume we deployed to Prod. We would have run Web.Prod.config, and Web.Release.config. It's obvious those files should be deleted.

But how can we tell that Web.config should be kept, while Web.Dev.config shouldn't? I.e., how do we know which files are transforms and which files aren't?

Will the decision be based on the existence of:

xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform"

On the root node?

[nblumhardt]

Perhaps we'd be better off introducing a Delete files feature, so you could just specify Web.*.config; Views\Web.*.config as the file list and match everything that needs to be cleaned up.

Doing it this way would be more generally useful, anyway.

[daniellittledev]

This feature will need a method to exclude files or be based off a white list. It's common to have other .config files match this pattern e.g. Web.log4net.config.

[PaulStovell]

Perhaps something like the TeamCity approach of + and -?

+:*.config
-:*.log4net.config

[daniellittledev]

Added Clean-Files PowerShell Step Template OctopusDeploy/Library#37

[nblumhardt]

@lavinski I think that makes this item closeable, since the solution doesn't directly address what's on this ticket. Let's follow up via the PR.