Craftsman at Work

I'm Artur Karbone, coding software architect and independent IT consultant and this is my blog about craftsmanship, architecture, distributed systems, management and much more.

Learn Octopus Deploy Part 9: Observe Config Values via Deployment Artifacts

My experience shows that sometimes for troubleshooting it is pretty handy to know what configuration parameters have been deployed. There is a couple of ways to obtain this info:

  • Octopus keeps variables snapshot per release
  • Login to the deployment target
  • Store config files as deployment artifacts, like this for instance:

I prefer to see configuration files as deployment artifacts. In Octopus Deployment it is doable via Post-deployment scripts. Just leverage the built-in New-OctopusArtifact function:

New-OctopusArtifact -Path "connections.config" -Name "connections.config" New-OctopusArtifact -Path "nlog.config" -Name "nlog.config" New-OctopusArtifact -Path "settings.config" -Name "settings.config"

To have this option/feature, enable it explicitly:

comments powered by Disqus