Enable dependency flow of secret-manager to engineering services repositories - Githubissues

dotnet / dnceng

.NET Engineering Services

MIT License

25 stars 18 forks source link

Enable dependency flow of secret-manager to engineering services repositories #764

Open riarenas opened 1 year ago

riarenas commented 1 year ago

Currently we don't have automatic updates of the secret-manager tooling in eng services repositories.

The instructions for enabling this in a repo are simple:

add an entry to version.details.xml
add an entry to .config./dotnet-tools.json
Create a subscription for the ".NET Eng Services - Int" or ".NET Eng Services - Prod" channels depending on whether we want to update for every main build or every production build.

This simplifies the process of pushing updates.

[ ] Arcade
[ ] Helix-machines
[ ] Helix-service
[ ] Dnceng itself (do we need/want this loop? this one is less necessary but might be nice for consistency?)

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[ ] Internal Infrastructure Improvements
Release Note Description

dougbu commented 1 year ago

suggest covering the dnceng outputs generally as part of this work. the list of assets produced (see https://maestro-prod.westus2.cloudapp.azure.com/679/https:%2F%2Fgithub.com%2Fdotnet%2Fdnceng/latest/graph) looks manageable