-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Fleet] Fix preconfigured remote ES outputs with secrets #172550
[Fleet] Fix preconfigured remote ES outputs with secrets #172550
Conversation
Pinging @elastic/fleet (Team:Fleet) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
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, should we add a testcase for updating a remote es preconfig and comparing the secret with hashes?
Hey @juliaElastic I added the fix for remote ES output update (was broken, as discussed on Slack). I agree that unit tests should ideally be amended as they failed to pick that up (even though they did exist for remote ES outputs). |
Thanks for fixing! |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
Summary
Closes #172546
Testing
GET .fleet-secrets/_search
. Check that the service token secret was created.