-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fix: bad substitution of API key #24036
Conversation
Pinging @elastic/agent (Team:Agent) |
Pinging @elastic/ingest-management (Team:Ingest Management) |
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Log outputExpand to view the last 100 lines of log output
💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
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.
👍
@@ -39,6 +39,7 @@ | |||
- Increase checkin grace period to 30 seconds {pull}23568[23568] | |||
- Fix libbeat from reporting back degraded on config update {pull}23537[23537] | |||
- Fix issues with dynamic inputs and conditions {pull}23886[23886] | |||
- Fix bad substitution of API key. {pull}24036[24036] |
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.
Is this required? I assume the fix goes into the same version (7.12
) as the changes that broke the setup.
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 don't have a strong opinion about it. This is a change (bugfix) hence the CHANGELOG entry. I will backport it to 7.x
once this is merged.
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.
Maybe I am not up-to-date with how this works in the beats repo, but since Changelog entries are usually user facing, I am used to only include bugfixes that are user facing (which is not the case if introduced & fixed in the same version). Up to you though whether or not to keep it.
/packaging |
Errors unrelated. |
* Fix: bad substitution of API key * Update changelog (cherry picked from commit 8ea9a95)
…-arm * upstream/master: [Metricbeat][Kubernetes] Extend state_node with more conditions (elastic#23905) [CI] googleStorageUploadExt step (elastic#24048) Check fields are documented for aws metricsets (elastic#23887) Update go-concert to 0.1.0 (elastic#23770) [Libbeat][New Processor] XML Decode (elastic#23678) Fix: bad substitution of API key (elastic#24036) [Filebeat] Add Pensando DFW Module (elastic#21063) [Filebeat] Check if processor is supported by ES version (elastic#23763) Syslog system tests: be more forgiving (elastic#24021)
What does this PR do?
This PR fixes the bad substitution (typo), spotted in https://beats-ci.elastic.co/job/Ingest-manager/job/elastic-package/job/PR-246/45/artifact/build/elastic-stack-dump/stack/logs/elastic-agent.log .
Why is it important?
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Related issues