mirror of
https://github.com/rust-lang/cargo.git
synced 2025-09-25 11:14:46 +00:00
5c87c14f9a
This is to bring us into conformance with the [Rust crate ownership policy](https://forge.rust-lang.org/policies/crate-ownership.html). Items of note - `cargo-credential-1password` is declared as Experimental as it is intended for the community but I was unsure if we wanted to commit to full support for it. In my mind, the ideal thing to do would be to expatriate this to 1password. - `home` is declared as Internal despite its wide use within the ecosystem. - `cargo-credential` is declared as Intentional as its an API intended for the wider ecosystem and I didn't see a reason to declare it experimental. - `cargo-platform`, `cargo-util-schemas`, and `crates-io` are declared as Intentional as they are both used internally and intended for others to use for logic that integrates with cargo/registries. I wondered about these being Experimental or Internal instead.
cargo-credential-1password
A Cargo credential provider for 1password.
This crate is maintained by the Cargo team as a part of an experiment around 1password integration. We encourage people to try to use this crate in their projects and provide feedback through issues, but do not guarantee long term maintenance.
Usage
cargo-credential-1password uses the 1password op CLI to store the token. You
must install the op CLI from the 1password
website.
Afterward you need to configure cargo to use cargo-credential-1password as
the credential provider. You can do this by adding something like the following
to your cargo config file:
[registry]
global-credential-providers = ["cargo-credential-1password --account my.1password.com"]
Finally, run cargo login to save your registry token in 1password.
CLI Arguments
cargo-credential-1password supports the following command-line arguments:
--account: The account name to use. For a list of available accounts, runop account list.--vault: The vault name to use. For a list of available vaults, runop vault list.