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

Deploy install scripts to dotnetcli account #558

Open
richlander opened this issue Dec 27, 2024 · 12 comments
Open

Deploy install scripts to dotnetcli account #558

richlander opened this issue Dec 27, 2024 · 12 comments

Comments

@richlander
Copy link
Member

We need to deploy the install scripts so that they are accessible via our CDN.

$ curl -LOv https://dot.net/v1/dotnet-install.sh
< HTTP/2 301
< date: Fri, 27 Dec 2024 06:16:22 GMT
< server: Kestrel
< location: https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.sh

After recent experiences, we've realized that our website should not be part of our high availability story for installers (via the install script). The CDN is already necessarily part of that. We should limit moving parts as much as possible.

/cc @mmitche

@richlander richlander changed the title Deploy installs script to dotnetcli account Deploy install scripts to dotnetcli account Dec 27, 2024
@mmitche
Copy link
Member

mmitche commented Dec 31, 2024

Completely agree.

@baronfel
Copy link
Member

baronfel commented Jan 6, 2025

To me this means

  • identify a storage bucket to deploy the scripts to
  • have pipelines (manually) publish to the bucket
  • backend network configuration to point CDNs to the bucket

These things all require access, yes? My team does not currently - we may need help to get these things done on the short term.

@richlander
Copy link
Member Author

That all checks out.

@mmitche @rbhanda @leecow -- can you help with these things?

@mmitche
Copy link
Member

mmitche commented Jan 7, 2025

I don't have perms to do so, but @rbhanda and @leecow do.

@mmitche
Copy link
Member

mmitche commented Jan 7, 2025

Recommendation for the install script location:

/dotnet/scripts/v1/*

Which would end up being:

builds.dotnet.microsoft.com/dotnet/scripts/v1/dotnet-install.ps1

@richlander
Copy link
Member Author

That sounds perfect.

https://dot.net/v1/dotnet-install.ps1 -> https://builds.dotnet.microsoft.com/dotnet/scripts/v1/dotnet-install.ps1

@rbhanda
Copy link

rbhanda commented Jan 7, 2025

https://builds.dotnet.microsoft.com/dotnet/scripts/v1/dotnet-install.ps1 is now available

@baronfel
Copy link
Member

baronfel commented Jan 7, 2025

Thanks @rbhanda! I verified that

  • dotnet-install.ps1
  • dotnet-install.sh
  • dotnet-install.sig

are available. However dotnet-install.asc is not. EDIT: it's been uploaded now, thanks!

What resources are being served with the new url, and where are they located? Thinking about what changes to the internal pipelines we'll need to start looking at.

@richlander
Copy link
Member Author

Could you create a new repo MD file that describes the intended production deployment, covering:

  • Source of all the files
  • Where they are deployed (blob storage and the website)
  • Where they can be accessed (CDN and website for compat but not recommended)
  • The short links that can be used to access them
  • Any guidance on whether we recommend using the short links or if that's just convenience
  • How the .sig and .asc files can be used

@baronfel
Copy link
Member

baronfel commented Jan 7, 2025

All of that content currently lives at https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-install-script (which we should update with the new urls once they are fully-prepped).

@richlander
Copy link
Member Author

It is hard to see the trees among the forest in that document. I think we need a terse doc that makes it very clear what our intent is. Also, we don't need to document the website location in docs, but we need to here.

@richlander
Copy link
Member Author

Do you want me to start this doc @baronfel?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants