0

Release Management always had the concept of "components", which are units of deployment that can be independently configured in the pipeline. Each component could have a number of stage-specific configuration variables, that could be configured in the component itself, like this:

enter image description here

Then, in the template instance, these could be set to different values depending on the stage:

enter image description here

But on the vNext components, required for the new vNext templates that use PowerShell DSC or Chef, these configuration variables don't exist anymore:

enter image description here

Are stage-specific configuration variables not supported anymore in RM? Am I responsible for setting these variables myself using PowerShell inside the configuration script now?

julealgon
  • 7,072
  • 3
  • 32
  • 77

1 Answers1

1

vNext components don't support tokenized configuration files. I think the idea is that setting the application's configurations are going to be handled via DSC, instead of via RM. I noticed the same thing when I was playing with DSC deployments.

Old-style components still support tokenized configuration files.

Daniel Mann
  • 57,011
  • 13
  • 100
  • 120
  • So the idea is to change the web.config files properties with a DSC resource, or something along those lines? – julealgon Oct 24 '14 at 19:08
  • You can either use the configuration script where the DSC variables are defined, or have the variables defined in the components tab as you just figured. These variables will be available to your PS/DSC script that you run via the Deploy using PS action. – divyanshm Oct 29 '14 at 07:05