Skip to content

Secret management for Azure Pipelines #958

Open
@matkoch

Description

@matkoch

Description

Given Azure CLI is present and the user is authenticated. The nuke :secrets command could set the secret variable directly in Azure DevOps.

  • Get organization and project from Git Remote
    [email protected]:v3/<organization/<project>/<repo-name>
    
  • Let user choose from pipelines (if more than one)
    az pipelines list --organization <organization> --project <project>
    
  • Set secret value
    az pipelines variable create --name <secret-name> --value <secret-value> --organization <organization> --project <project> --pipeline-name <pipeline>
    

Usage Example

See https://nuke.build/docs/global-tool/secrets/

Alternative

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions