-
Notifications
You must be signed in to change notification settings - Fork 187
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
docs: Add password-protected SSH keys information #801
Conversation
@@ -152,7 +152,7 @@ data: | |||
#### SSH authentication | |||
|
|||
To authenticate towards a Git repository over SSH, the referenced Secret is | |||
expected to contain `.data.identity` and `known_hosts` fields. With the respective | |||
expected to contain `identity` and `known_hosts` fields. With the respective |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed .data.
to align with the approach with known_hosts
. Alternatively, we could add the .data.
prefix on both.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should be using stringData
in examples, since flux create secret
generates secrets that way, so GitHub and others will alert when you push unencrypted tokens. We should tell people to use flux create secret --export
especially for Git where the CLI helps generating know hosts like SC expects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the example, but did not mention the data
/stringData
conundrum, as we support both and it will come down to user preference.
Also added a Flux CLI example for SSH secret creation. PTAL
Signed-off-by: Paulo Gomes <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks @pjbgf
Similar information is present for older versions of the API, however, not for the latest, which affects the live documentation.