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

[Proposal] Credentials per project (local .cargo/credentials) #4645

Closed
fa7ca7 opened this issue Oct 19, 2017 · 2 comments
Closed

[Proposal] Credentials per project (local .cargo/credentials) #4645

fa7ca7 opened this issue Oct 19, 2017 · 2 comments

Comments

@fa7ca7
Copy link
Contributor

fa7ca7 commented Oct 19, 2017

Docs prescribe a user to do login first, so during publish, owner or yank cargo should already have credentials. Do we actually need --token parameter?

Probably it'd be better to implement local .cargo/credentials instead as discussed in #3978 (at the end of thread)? Local credentials will override the global.

For user it might look like:

$ cargo login token  # save to .cargo/credentials
$ cargo login --global token  # save to $HOME/.cargo/credentials
@fa7ca7 fa7ca7 changed the title What is the significance of specifying --token parameter? [Proposal] Credentials per project (local .cargo/credentials) Oct 31, 2017
@stale
Copy link

stale bot commented Sep 19, 2018

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

  • Is this still relevant?
  • If so, what is blocking it?
  • Is it known what could be done to help move this forward?

Thank you for contributing!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

@stale stale bot added the stale label Sep 19, 2018
@stale
Copy link

stale bot commented Oct 19, 2018

As I didn't see any updates in 30 days I'm going to close this. Please see the previous comment for more information!

@stale stale bot closed this as completed Oct 19, 2018
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

1 participant