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

Remove .net 6 runtime requirement from dotnet-helix-service #2412

Open
chcosta opened this issue Apr 1, 2024 · 3 comments
Open

Remove .net 6 runtime requirement from dotnet-helix-service #2412

chcosta opened this issue Apr 1, 2024 · 3 comments
Labels
Ops - Service Maintenance Used to track issues related to maintaining the services .NET Eng Supports

Comments

@chcosta
Copy link
Member

chcosta commented Apr 1, 2024

Dotnet-helix-service has a requirement on the .NET 6 runtime because it utilizes secret-manager, which is not yet updated to .NET 8 support. AFTER #1430 is completed and secret-manager targets .NET 8, we should remove these additional runtime installs from the dotnet-helix-service build.

Sample .NET 6 runtime install - https://dev.azure.com/dnceng/internal/_git/dotnet-helix-service?path=/eng/deploy.yaml&version=GBmain&line=30&lineEnd=34&lineStartColumn=1&lineEndColumn=23&lineStyle=plain&_a=contents

There are more locations in the repo which also install 6.0 and should be updated.

@ilyas1974 ilyas1974 added the Ops - Service Maintenance Used to track issues related to maintaining the services .NET Eng Supports label May 21, 2024
@ilyas1974 ilyas1974 added Ops - P1 Operations task, priority 1 (highest priority) Ops - Spike Work items to be included in our Ops Spike and removed Ops - P1 Operations task, priority 1 (highest priority) labels Jul 24, 2024
@riarenas
Copy link
Member

This issue depends on an issue that is not part of the spike: #2413

@markwilkie @ilyas1974 Should #2413 be moved to the spike, or this issue removed? (With the understanding that this would add at least 2 or 3 weeks to the spike)?

@ilyas1974
Copy link
Contributor

I think this can be removed from the spike (Mark can confirm). Our services will not stop working, we just won't be getting updating.

@riarenas
Copy link
Member

riarenas commented Sep 3, 2024

Agreed. I can't find anything that would break underneath us, other than getting more CG alerts. Removing from the Spike.

@riarenas riarenas removed the Ops - Spike Work items to be included in our Ops Spike label Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ops - Service Maintenance Used to track issues related to maintaining the services .NET Eng Supports
Projects
None yet
Development

No branches or pull requests

3 participants