-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Simplify JWK download by using curl directly from backend #281
Conversation
🧪 Details on macOS Unix 14.5.0✅ Devlooped.Tests.SponsorLinkTests.TryRead 🧪 Details on Ubuntu 22.04.4 LTS✅ Devlooped.Tests.SponsorLinkTests.TryRead 🧪 Details on Microsoft Windows 10.0.20348✅ Devlooped.Tests.SponsorLinkTests.TryRead from dotnet-retest on .NET 8.0.7 with 💜 |
173de0e
to
531cb12
Compare
NOTES: 1. `pwsh` cannot be replaced with `powershell` because the output of `curl` is different and breaks `jq` 2. `jq` would still be needed even if replacing `pwsh` 3. Downloading the `jwk` directly from sponsorlink.devlooped.com is done via curl. This is suboptimal and slower (typically) than downloading from github, hence it's used as a fallback only. 4. If no curl is available (legacy windows?), use built-in powershell. This guarantees we can always download the JWK.
Our backend at https://sponsorlink.devlooped.com/jwk basically does the same we were doing in MSBuild before: download from GH the JWT and extract the JWK info. Since the backend needs to be up anyway, just simplify the build and use it.
Simplify JWK download by using curl directly from backend