-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: fix linting issues exposed by fixing golangci-lint (#12895)
Co-authored-by: Marko <marbar3778@yahoo.com> Co-authored-by: Julien Robert <julien@rbrt.fr>
- Loading branch information
1 parent
15b04c2
commit 0943a70
Showing
148 changed files
with
571 additions
and
469 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,40 +1,40 @@ | ||
// Package keys provides common key management API. | ||
// | ||
// | ||
// The Keyring interface | ||
// # The Keyring interface | ||
// | ||
// The Keyring interface defines the methods that a type needs to implement to be used | ||
// as key storage backend. This package provides few implementations out-of-the-box. | ||
// | ||
// NewInMemory | ||
// # NewInMemory | ||
// | ||
// The NewInMemory constructor returns an implementation backed by an in-memory, goroutine-safe | ||
// map that has historically been used for testing purposes or on-the-fly key generation as the | ||
// generated keys are discarded when the process terminates or the type instance is garbage | ||
// collected. | ||
// | ||
// New | ||
// # New | ||
// | ||
// The New constructor returns an implementation backed by a keyring library | ||
// (https://github.com/99designs/keyring), whose aim is to provide a common abstraction and uniform | ||
// interface between secret stores available for Windows, macOS, and most GNU/Linux distributions | ||
// as well as operating system-agnostic encrypted file-based backends. | ||
// | ||
// The backends: | ||
// os The instance returned by this constructor uses the operating system's default | ||
// credentials store to handle keys storage operations securely. It should be noted | ||
// that the keyring keyring may be kept unlocked for the whole duration of the user | ||
// session. | ||
// file This backend more closely resembles the previous keyring storage used prior to | ||
// v0.38.1. It stores the keyring encrypted within the app's configuration directory. | ||
// This keyring will request a password each time it is accessed, which may occur | ||
// multiple times in a single command resulting in repeated password prompts. | ||
// kwallet This backend uses KDE Wallet Manager as a credentials management application: | ||
// https://github.com/KDE/kwallet | ||
// pass This backend uses the pass command line utility to store and retrieve keys: | ||
// https://www.passwordstore.org/ | ||
// test This backend stores keys insecurely to disk. It does not prompt for a password to | ||
// be unlocked and it should be use only for testing purposes. | ||
// memory Same instance as returned by NewInMemory. This backend uses a transient storage. Keys | ||
// are discarded when the process terminates or the type instance is garbage collected. | ||
// | ||
// os The instance returned by this constructor uses the operating system's default | ||
// credentials store to handle keys storage operations securely. It should be noted | ||
// that the keyring keyring may be kept unlocked for the whole duration of the user | ||
// session. | ||
// file This backend more closely resembles the previous keyring storage used prior to | ||
// v0.38.1. It stores the keyring encrypted within the app's configuration directory. | ||
// This keyring will request a password each time it is accessed, which may occur | ||
// multiple times in a single command resulting in repeated password prompts. | ||
// kwallet This backend uses KDE Wallet Manager as a credentials management application: | ||
// https://github.com/KDE/kwallet | ||
// pass This backend uses the pass command line utility to store and retrieve keys: | ||
// https://www.passwordstore.org/ | ||
// test This backend stores keys insecurely to disk. It does not prompt for a password to | ||
// be unlocked and it should be use only for testing purposes. | ||
// memory Same instance as returned by NewInMemory. This backend uses a transient storage. Keys | ||
// are discarded when the process terminates or the type instance is garbage collected. | ||
package keyring |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.