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.

Sign up for GitHub

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

Jump to bottom

Tracking Issue for RFC 3139: Private Registrys #10523

Closed
Eh2406 opened this issue Mar 30, 2022 · 1 comment
Closed

Tracking Issue for RFC 3139: Private Registrys #10523

Eh2406 opened this issue Mar 30, 2022 · 1 comment
Labels
C-tracking-issue Category: A tracking issue for something unstable.

Comments

@Eh2406
Copy link
Contributor

Eh2406 commented Mar 30, 2022

Summary

RFC: #3139
Implementation: #NNNN
Documentation: #NNNN

Enables Cargo to include the authorization token for all API requests, crate downloads and index updates (when using HTTP) by adding a configuration option to config.json in the registry index.

Unresolved Issues

No response

Future Extensions

No response

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
@Eh2406 Eh2406 added the C-tracking-issue Category: A tracking issue for something unstable. label Mar 30, 2022
@Eh2406
Copy link
Contributor Author

Eh2406 commented Mar 30, 2022

dup of #10474

@Eh2406 Eh2406 closed this as completed Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-tracking-issue Category: A tracking issue for something unstable.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Eh2406