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:
class RunPipelineParameters(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 = resources
self.variables = variablesReactions are currently unavailable
azure-devops/azure/devops/v6_0/pipelines/pipelines_client.py takes the parameter run_parameters and then sets the variable content via
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: