Improve messaging when NuGet service(s) are degraded
Anand Gaurav edited this page May 17, 2018
·
2 revisions
Pages 155
Home
Contributing
Specs
Incubation
Reviewing
- Centrally-managing-NuGet-package-versions
- Package Applicability
- dotnet list package --vulnerable
- Machine-readable output for dotnet list package
- Support Package Renames
- Advanced Search on NuGet.org
Reviewed
Implemented
- Enhanced package upload workflow
- Register package signing certificates
- Organizations on NuGet.org
- 2 Factor Auth for NuGet.org sign in
- Add nuget sources command to the dotnet CLI
- Author Package Signing
- Backporting PC to msbuild restore
- Deprecate packages
- Dotnet list package
- Enable repeatable package restore using lock file
- NuGet Client Package Debugging
- NuGet Package Debugging & Symbols Improvements
- NuGet Package Identity Verification
- NuGet Package Signing Client Policy
- NuGet Sign Command
- NuGet Verify Command
- Storing trusted repository
- Package Signatures Technical Details
- Package signing
- Packages.config SHA Validation
- Packaging Icon, License and Documentation within the nupkg
- Repository Signatures and Countersignatures Technical Specification
- Repository Signatures
- Show outdated packages
- Symbols Package Upload and Delete Workflow
Templates
Clone this wiki locally
Requirements
-
When one or more NuGet services are degraded,
- Auto update the status page
- Auto update the NuGet.org page with the status message with link to status page
- Should not refresh and remove the degraded status
-
Show the package submission time on the status page
- Package validation time
- Indexing time
Proposal
Services that should be monitored for auto update of the status page
NuGet Gallery notifications
Status page
- Collapse service categories by default. Expand if one of the components/services in the category is degraded.
- V2 and V3 endpoints cleanup in the Service section
- CDN status
- Improve the status messaging - should not auto refresh to Green.