-
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
[7.17](backport #35551) [Heartbeat] Remove synthetics support for ironbank #35588
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* [Heartbeat] Remove synthetics support for ironbank * ci: remove heartbeat ironbank validation * ci: remove heartbeat ironbank validation scheduler * remove heartbeat ironbank * avoid running it * Revert "ironbank: support for heartbeat (#32954)" This reverts commit 544cfd6. * Revert "Revert "ironbank: support for heartbeat (#32954)"" This reverts commit 1e6b816. * Revert "avoid running it" This reverts commit 0c533e7. * Revert "remove heartbeat ironbank" This reverts commit afa51b7. * Revert "ci: remove heartbeat ironbank validation scheduler" This reverts commit e34fa74. * Revert "ci: remove heartbeat ironbank validation" This reverts commit b0e0ad0. * update version --------- Co-authored-by: Victor Martinez <VictorMartinezRubio@gmail.com> (cherry picked from commit 3f5afa5) # Conflicts: # dev-tools/packaging/templates/ironbank/heartbeat/hardening_manifest.yaml
mergify
bot
added
backport
conflicts
There is a conflict in the backported pull request
labels
May 26, 2023
mergify
bot
requested review from
rdner and
cmacknz
and removed request for
a team
May 26, 2023 08:14
botelastic
bot
added
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
May 26, 2023
emilioalvap
added
the
Team:obs-ds-hosted-services
Label for the Observability Hosted Services team
label
May 26, 2023
Pinging @elastic/uptime (Team:Uptime) |
botelastic
bot
removed
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
May 26, 2023
Collaborator
This pull request has not been merged yet. Could you please review and merge it @emilioalvap? 🙏 |
/test |
/package |
1 similar comment
/package |
This pull request has not been merged yet. Could you please review and merge it @emilioalvap? 🙏 |
This pull request has not been merged yet. Could you please review and merge it @emilioalvap? 🙏 |
/test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport
conflicts
There is a conflict in the backported pull request
Team:obs-ds-hosted-services
Label for the Observability Hosted Services team
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automatic backport of pull request #35551 done by Mergify.
Cherry-pick of 3f5afa5 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com