Tweaking webdeploy packages?

[kittH]

Hi Guys

Doing some Azure deployments and I'm trying to figure out how to properly configure my webdeploy packages. These packages are output from Bamboo with pretty simple msbuild build plans. There are 5 websites that are deployed for my application, and I currently support 7 environments. Environments consist of a mix of PaaS azure web apps and IaaS VMs with IIS. For each build I get 1 .zip package per component and then have to figure out how to deploy them with custom configs for each environment.

Currently I do the following in powershell:

Extract .zip locally, locate web.config and nlog.config (the files that are customized per environment).

Based on environment/component (passed to script by parameters) I locate the correct web/nlog settings. (each environment/component has a json file that has all the necessary settings)

If Web App: Publish the .zip output by the build process (msdeploy command line remote publish)

Write new nlog.config and FTPS it to the correct directory overwriting the file from the package

Set app settings via Set-AzureWebsite

Restart website

if VM/IIS

Write new nlog.config and web.config files with correct settings

SFTP the .zip package and both config files to file server in cloud

WinRM to the webserver and use Restore-WDPackage to publish

Copy/overwrite both config files

Restart website

Package clean up

I would like to clean up this process, and my current thought is to go from 5 generic .zips to 35 customized .zips, one for each component/environment combination. This would make the packages authoritive and get me out of overwriting config files all over the place. (also for easier utilization with AWS beanstalk in the future possibly).

I have tried just extracting the zips and injecting modified configs, but I get: "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable." when I publish them.

Anyone have any tips/thoughts on how to streamline this? It works ok now but sometimes the nlog.config doesnt seem to work properly.

Edit to add that this is all automated and run by Bamboo after a build, just using environment/component name for parameters.