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

Not all internal builds need access to the secrets variable group #1444

Open
lbussell opened this issue Sep 23, 2024 · 2 comments
Open

Not all internal builds need access to the secrets variable group #1444

lbussell opened this issue Sep 23, 2024 · 2 comments

Comments

@lbussell
Copy link
Contributor

The common pipeline variable template always references the secrets variable group. However, not every pipeline using the internal template needs this secrets variable group:

- group: DotNet-Docker-Common
- ${{ if eq(variables['System.TeamProject'], 'internal') }}:
- group: DotNet-Docker-Secrets-WIF

We should find another way to condition this, so that we can exclude it for some pipelines such as cg-detection.yml.

Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

1 similar comment
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@lbussell lbussell moved this from Backlog to Post Release in .NET Docker Sep 23, 2024
@lbussell lbussell added the wave2 label Sep 23, 2024
@lbussell lbussell moved this from Post Release to Current Release in .NET Docker Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Current Release
Development

No branches or pull requests

1 participant