The Tokenizer task documentation mentions that the json file can have multiple <release environment name> sections in it. Currently it seems that the <release environment name> specified in the json file must exactly match the Environment name used in the VSTS Release Management release definition. Is there anyway to override that? Perhaps by overriding a RM variable or something? It would be nice to be able to pass that environment value into the Tokenizer task, where it would use the specified value and fallback to the VSTS Release Management Environment name if none was provided.
This would be helpful for quite a few scenarios. For example, we have several datacenters in each of our environments, and we don't always want to deploy to every datacenter in an environment at the same time, so we'll have separate RM Environments for each datacenter. From the Tokenizer Json file's perspective, all of the settings for the different datacenters in the same environment will match, so with the current implementation it means we'll need to duplicate all of that environment configuration in the json file for each datacenter. If we could specify the json environment to use on the Tokenizer task, we'd be able to just have the environment defined in the json file once, and use that environment name for each of our different RM Environments.
The Tokenizer task documentation mentions that the json file can have multiple
<release environment name>sections in it. Currently it seems that the<release environment name>specified in the json file must exactly match the Environment name used in the VSTS Release Management release definition. Is there anyway to override that? Perhaps by overriding a RM variable or something? It would be nice to be able to pass that environment value into the Tokenizer task, where it would use the specified value and fallback to the VSTS Release Management Environment name if none was provided.This would be helpful for quite a few scenarios. For example, we have several datacenters in each of our environments, and we don't always want to deploy to every datacenter in an environment at the same time, so we'll have separate RM Environments for each datacenter. From the Tokenizer Json file's perspective, all of the settings for the different datacenters in the same environment will match, so with the current implementation it means we'll need to duplicate all of that environment configuration in the json file for each datacenter. If we could specify the json environment to use on the Tokenizer task, we'd be able to just have the environment defined in the json file once, and use that environment name for each of our different RM Environments.