This repository has been archived by the owner on Sep 17, 2024. It is now read-only.
feat: add first scenario for Fleet Server (backport #900) #1056
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
* chore: capture Fleet's default policy in a stronger manner * chore: support passing the field for is_default policy * chore: remove inferred type for array * chore: enable fleet server in kibana config * chore: create fleet config struct This type will hold information about Fleet config, supporting building the proper flags during enrollment * chore: refactor enroll command logic to use the new struct * chore: check if the fleet-server field exists when retrieving the policy * chore: refactor install to support fleet-server The flags used for installing/enrolling an agent will be generated from the new FleetConfig struct. Because of that, we are moving a pointer to that fleet config to the install command * feat: add first scenario for fleet server * chore: add fleet server branch to the CI * chore: set Then clause for the scenario * chore: remove step * fix: define fallback when checking agent status * chore: simplify creation of Fleet configs * fix: forgot to rename variable * WIP * chore: rename scenario * fix: wrong merge conflicts resolution * chore: support passing environment when running a command in a container * chore: run elastic agent commands passing an env * WIP * chore: separate bootstrapping an agent from connecting to a fleet server agent * fix: use proper fleet-server flags Co-authored-by: Adam Stokes <[email protected]> (cherry picked from commit a150734)
|
I think we are missing this backport: #1036 |
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Test errors
Expand to view the tests failures
|
| Test | Results |
|---|---|
| Failed | 5 |
| Passed | 115 |
| Skipped | 0 |
| Total | 120 |
Genuine test errors 
💔 There are test failures but not known flaky tests, most likely a genuine test failure.
- Name:
Initializing / End-To-End Tests / ubuntu-18.04_fleet_stand_alone_agent / [empty] – TEST-fleet.xml - Name:
Initializing / End-To-End Tests / ubuntu-18.04_fleet_fleet_server / [empty] – TEST-fleet.xml - Name:
Initializing / End-To-End Tests / ubuntu-18.04_fleet_agent_endpoint_integration / [empty] – TEST-fleet.xml - Name:
Initializing / End-To-End Tests / ubuntu-18.04_fleet_fleet_mode_agent / [empty] – TEST-fleet.xml - Name:
Initializing / End-To-End Tests / ubuntu-18.04_fleet_backend_processes / [empty] – TEST-fleet.xml
|
Failures are caused by latest kibana snapshot. #1055 will fix that version |
8 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 #900 done by Mergify.
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 refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill 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.io/