This repository has been archived by the owner on Sep 17, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 42
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: add first scenario for Fleet Server (#900)
* 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)
- Loading branch information
1 parent
5f826f0
commit c812883
Showing
8 changed files
with
235 additions
and
45 deletions.
There are no files selected for viewing
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
@fleet_server | ||
Feature: Fleet Server | ||
Scenarios for Fleet Server, where an Elasticseach and a Kibana instances are already provisioned, | ||
so that the Agent is able to communicate with them | ||
|
||
@start-fleet-server | ||
Scenario Outline: Deploying an <os> Elastic Agent that starts Fleet Server | ||
When a "<os>" agent is deployed to Fleet with "tar" installer in fleet-server mode | ||
Then the agent is listed in Fleet as "online" | ||
|
||
@centos | ||
Examples: Centos | ||
| os | | ||
| centos | | ||
|
||
@debian | ||
Examples: Debian | ||
| os | | ||
| debian | |
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
Oops, something went wrong.