v2.51.1

Compare Source

Pull Requests | Issues | aquaproj/aqua@v2.51.0...v2.51.1

Features

#​3852 #​3853 Support managing a GitHub access token using Keyring

You can now manage a GitHub Access token using secret store such as Windows Credential Manager, macOS Keychain, and GNOME Keyring.

1. Configure a GitHub Access token by aqua token set command:

$ aqua token set
Enter a GitHub access token: # Input GitHub Access token

or you can also pass a GitHub Access token via standard input:

echo "<github access token>" | aqua tokn set -stdin

2. Enable the feature by setting the environment variable AQUA_KEYRING_ENABLED:

export AQUA_KEYRING_ENABLED=true

Note that if the environment variable GITHUB_TOKEN is set, this feature gets disabled.

You can remove a GitHub Access token from keyring by aqua token rm command:

aqua token rm

v2.51.0

Compare Source

Pull Requests | Issues | aquaproj/aqua@v2.50.1...v2.51.0

[!WARNING]
We intended to add a new command token in this release, but we forgot it.
We'll release v2.51.1 soon.

Features

#​3852 Support managing a GitHub access token using Keyring

You can now manage a GitHub Access token using secret store such as Windows Credential Manager, macOS Keychain, and GNOME Keyring.

1. Configure a GitHub Access token by aqua token set command:

$ aqua token set
Enter a GitHub access token: # Input GitHub Access token

or you can also pass a GitHub Access token via standard input:

echo "<github access token>" | aqua tokn set -stdin

2. Enable the feature by setting the environment variable AQUA_KEYRING_ENABLED:

export AQUA_KEYRING_ENABLED=true

Note that if the environment variable GITHUB_TOKEN is set, this feature gets disabled.

You can remove a GitHub Access token from keyring by aqua token rm command:

aqua token rm