Skip to content

uses wildcard in az pipelines variable-group list --group-name causes weird behavior #27169

@bill-kan-codebox

Description

@bill-kan-codebox

Describe the bug

if i run az pipelines variable-group list --group-name dev* such that group-name uses wildcard * then these fields are null but they should not be null.

    "name": "dev-docker",
    "modifiedBy": {
........
      "displayName": null,
      "uniqueName": null,
.......
    },

    "name": "dev",
    "modifiedBy": {
........
      "displayName": fname lname,
      "uniqueName": name@email.com,
.......
    },

if i run az pipelines variable-group list --group-name dev-docker such that group-name specifies actual group name dev-docker then these fields have their value displayed.

    "modifiedBy": {
........
      "displayName": john smith,
      "uniqueName": jsmith@email.com,
.......
    },

Related command

az pipelines variable-group list

Errors

no error but values are not displayed when they should have values.

Issue script & Debug output

    "name": "dev-docker",
    "modifiedBy": {
........
      "displayName": null,
      "uniqueName": null,
.......
    },

    "name": "dev",
    "modifiedBy": {
........
      "displayName": fname lname,
      "uniqueName": name@email.com,
.......
    },

Expected behavior

they should be displayed.

Environment Summary

azure cli 2.50.1

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Auto-AssignAuto assign by botDevOpsPipelinesService AttentionThis issue is responsible by Azure service team.act-platform-engineering-squadbugThis issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-triageThis issue needs the team to triage.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions