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

Avoid displaying API key secret during cli configuration #114

Closed
ghost opened this issue May 26, 2020 · 0 comments · Fixed by #115
Closed

Avoid displaying API key secret during cli configuration #114

ghost opened this issue May 26, 2020 · 0 comments · Fixed by #115

Comments

@ghost
Copy link

ghost commented May 26, 2020

As a Lacework CLI user,
I need the configure command to avoid showing my API key secret,
So that I can protect my access to my Lacework account.

ghost pushed a commit that referenced this issue May 26, 2020
Closes #114

Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
ghost pushed a commit that referenced this issue May 26, 2020
When users configure the CLI and insert their API secret key, such
secret will now be formatted to avoid showing it on the screen.

Example:
```
$ lacework configure
▸ Account: tech-ally
▸ Access Key ID: TECHALLY_3ACE24322ABBD3AC4435608BACEC4D638BEC6500DC12345
▸ Secret Access Key: (*****************************f19e)

You are all set!
```

Closes #114

Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
@ghost ghost closed this as completed in #115 May 26, 2020
ghost pushed a commit that referenced this issue May 26, 2020
* feat(cli): avoid displaying API key secret

When users configure the CLI and insert their API secret key, such
secret will now be formatted to avoid showing it on the screen.

Example:
```
$ lacework configure
▸ Account: tech-ally
▸ Access Key ID: TECHALLY_3ACE24322ABBD3AC4435608BACEC4D638BEC6500DC12345
▸ Secret Access Key: (*****************************f19e)

You are all set!
```

Closes #114

Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
This issue was closed.
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

Successfully merging a pull request may close this issue.

0 participants