Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support Azure Pipeline Variable Groups in Push Extension

Open
#453 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure
Domain
ci-cd, devops

Research direction

Start by reviewing the Push extension's existing Secure files flow and the Azure Pipelines Variable Groups behavior described in the issue. Confirm how a Variable Group should be referenced and how sensitive values should be supplied; done means the Push task can consume a Variable Group without a separate secure-file download task.

Written by the indexing model from the issue text.

Description

Azure Pipelines enhancement

Currently we use the Push extension to seed configuration data when building new environments. We do not commit some of our configuration values to our repo because the data is considered sensitive.

To get around the current limitation in the push extension, we store the sensitive seed configuration file in the Pipelines "Secure files" library and then use a separate task to download the file before executing the Push task.

It would be incredibly helpful if we could just reference Pipeline Variable Groups directly.

Thanks!

Dominant language
No language data
Stars
263
Forks
82
Avg merge
3d 15h
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AppConfiguration

All issues in Azure/AppConfiguration

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.