-
Notifications
You must be signed in to change notification settings - Fork 4
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 build status and adjust Vault #1074
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 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.
I did a quick search for https://github.com/search?l=Groovy&q=org%3Aelastic+readSecret&type=Code and I couldn not find any other consumers
+1
…notify-message-template * upstream/master: Fix build status and adjust Vault (#1074) Remove super-linter since it takes 20 minutes (#1083) Bump elastic stack version automation (#1081) feat: step to check if a docker image exists (#1077) docs: update CHANGELOG.md [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release v1.1.210 Enable stage filter argument for the beatsStages (#1076)
…automation * upstream/master: Add searchIssuesWithFilters action for the lookForGitHubIssues (#1082) docs: update CHANGELOG.md [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release v1.1.211 Fix build status and adjust Vault (#1074) Remove super-linter since it takes 20 minutes (#1083)
What does this PR do?
This contains a variety of fixes which related to the Jenkins release job for the apm-java-agent project.
Build Status
The previous step used the standard library to make HTTP requests. However, it was silently failing and returning incorrect results. We change to use our existing HTTP client implementation which works more reliably and returns the correct result.
Make vault credentials configurable
The
internal-ci
machine is shared between multiple teams and our credentials are namespaced accordingly. Therefore, I modified the Vault implementation to make it possible to pass in specific IDs to use when authenticating to Vault.Why is it important?
Fixes issues related to the broken release job for the APM Java agent.
Related issues
https://github.com/elastic/observability-robots/issues/463