azure-devops/azure/devops/v6_0/pipelines/pipelines_client.py takes the parameter run_parameters and then sets the variable content via
content=self._serialize.body(run_parameters, 'RunPipelineParameters')
In doing so it discards templateParameters (along with previewRun, stagesToSkip, and yamlOverride), but my concern is with templateParameters.
If I'm tracing things correctly, the problem is in the class RunPipelineParameters in azure-devops/azure/devops/v6_0/pipelines/models.py which only maps resources and variables:
classRunPipelineParameters(Model):
""" :param resources: :type resources: :class:`RunResourcesParameters <azure.devops.v6_0.pipelines.models.RunResourcesParameters>` :param variables: :type variables: dict """_attribute_map= {
'resources': {'key': 'resources', 'type': 'RunResourcesParameters'},
'variables': {'key': 'variables', 'type': '{Variable}'}
}
def__init__(self, resources=None, variables=None):
super(RunPipelineParameters, self).__init__()
self.resources=resourcesself.variables=variables
azure-devops/azure/devops/v6_0/pipelines/pipelines_client.py takes the parameter
run_parametersand then sets the variable content viaIn doing so it discards templateParameters (along with previewRun, stagesToSkip, and yamlOverride), but my concern is with templateParameters.
If I'm tracing things correctly, the problem is in the class RunPipelineParameters in azure-devops/azure/devops/v6_0/pipelines/models.py which only maps resources and variables: