-
Notifications
You must be signed in to change notification settings - Fork 68
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
Add an introduction to FLEET_SERVER_ELASTICSEARCH_CA_TRUSTED_FINGERPRINT
#409
Conversation
💚 CLA has been signed |
This pull request does not have a backport label. Could you fix it @linghengqian? 🙏
|
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.
@linghengqian
Thanks very much for adding this!
I hope you don't mind that I pushed a commit directly to your branch so that the changes will appear in the docs, and I also added very small edits to use variables for the product names. Here's how it appears when I run a test build:
LGTM! 👍
I added a |
…RINT` (#409) (#410) * Add an introduction to `FLEET_SERVER_ELASTICSEARCH_CA_TRUSTED_FINGERPRINT` * Add include statement plus small edits --------- Co-authored-by: David Kilfoyle <david.kilfoyle@elastic.co> (cherry picked from commit b4717f8) Co-authored-by: Ling Hengqian <linghengqian@outlook.com>
Is this supposed to be a base64 encode of the sha-256 fingerprint? I would assume not since it does not explicitly say it, but I have seen other elastic documentation calling for the base64 of the ca trusted fingerprint. |
|
Understood @linghengqian , thank you! I hope to have a call with an elastic engineer next week, so I will definitely ask then. |
FLEET_SERVER_ELASTICSEARCH_CA_TRUSTED_FINGERPRINT
environment variable in documentation elastic-agent#311 .FLEET_SERVER_ELASTICSEARCH_CA_TRUSTED_FINGERPRINT
.