Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Azure Pipeline Variable Groups in Push Extension #453

Open
everettcomstock opened this issue Jan 22, 2021 · 3 comments
Open

Support Azure Pipeline Variable Groups in Push Extension #453

everettcomstock opened this issue Jan 22, 2021 · 3 comments
Labels
Azure Pipelines enhancement New feature or request

Comments

@everettcomstock
Copy link

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!

@zhenlan zhenlan added Azure Pipelines enhancement New feature or request labels Jan 25, 2021
@zhenlan
Copy link
Contributor

zhenlan commented Jan 25, 2021

@everettcomstock thanks for the suggestion. We will look into it.

@jiayi11 jiayi11 assigned jiayi11 and Yiming-Jia and unassigned jiayi11 Jan 25, 2021
@Yiming-Jia
Copy link
Contributor

@everettcomstock . Could you elaborate the scenario more? My understanding is that the sensitive data stored in secure file? And you want to move the data to variable group and use the push task to consume the data from variable group directly?

@everettcomstock
Copy link
Author

@Yiming-Jia, I think our ideal scenario would only rely on Pipeline Variable Groups. Values in the group can be stored as secrets. If the Push extension were able to access Pipeline variables, or variable groups directly, without the need of providing a file, I think that would work for our situation.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure Pipelines enhancement New feature or request
Projects
Development

No branches or pull requests

4 participants