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

feat: add default Scanner user #116

Closed

Conversation

agilgur5
Copy link
Contributor

@agilgur5 agilgur5 commented Aug 6, 2020

Description

  • set to the name "scanner"

  • also consistently use "user" in the docs instead of "username"

    • I read "username" and used that in my values in a live call with
      Aqua Engineers, which didn't work since it is actually "user"
      • this should make mistakes and confusion like that harder to happen

Tags

This will merge conflict with #112 because it changes the line above this 😕
Ran into the "user" vs. "username" thing right after hitting #103

Review Notes

I'm not totally sure why the Scanner user and password aren't specified as pre-requisites one must create in the docs. If it wasn't for Aqua Engineers telling me on a call, I wouldn't have done that or known to do so until I got the required error.

- set to the name "scanner"

- also consistently use "user" in the docs instead of "username"
  - I read "username" and used that in my values in a live call with
    Aqua Engineers, which didn't work since it is actually "user"
    - this should make mistakes and confusion like that harder to happen
@KoppulaRajender
Copy link
Collaborator

updated docs about user credentials prerequisite for scanner chart deployment. closing this PR, thanks!

@agilgur5
Copy link
Contributor Author

agilgur5 commented Jan 14, 2022

@KoppulaRajender I see #270 added docs for creating a Scanner, which did fix a portion of #119, but it does not replace this PR, which adds a default user and fixes some wording.

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 this pull request may close these issues.

None yet

2 participants