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
feat: add first scenario for Fleet Server #900
Merged
adam-stokes
merged 30 commits into
elastic:master
from
mdelapenya:438-fleet-server-scenarios
Apr 19, 2021
Merged
Changes from all commits
Commits
Show all changes
30 commits
Select commit
Hold shift + click to select a range
b1931c0
chore: capture Fleet's default policy in a stronger manner
mdelapenya 6f54550
chore: support passing the field for is_default policy
mdelapenya ad0d17f
chore: remove inferred type for array
mdelapenya e52c8b6
chore: enable fleet server in kibana config
mdelapenya e8bee02
chore: create fleet config struct
mdelapenya bb62c4f
chore: refactor enroll command logic to use the new struct
mdelapenya d8e57ce
chore: check if the fleet-server field exists when retrieving the policy
mdelapenya 6189bff
chore: refactor install to support fleet-server
mdelapenya d9da8b0
feat: add first scenario for fleet server
mdelapenya 830eb12
chore: add fleet server branch to the CI
mdelapenya eaa68f2
Merge branch 'master' into 438-fleet-server-scenarios
mdelapenya bc9e1ff
chore: set Then clause for the scenario
mdelapenya 4ae1019
chore: remove step
mdelapenya 721aa21
fix: define fallback when checking agent status
mdelapenya f5a9f46
chore: simplify creation of Fleet configs
mdelapenya eb8f013
fix: forgot to rename variable
mdelapenya e9edde9
Merge branch 'master' into 438-fleet-server-scenarios
mdelapenya 356750f
WIP
mdelapenya f2244ad
Merge branch 'master' into 438-fleet-server-scenarios
mdelapenya 7358928
chore: rename scenario
mdelapenya bcd69ee
Merge branch 'master' into 438-fleet-server-scenarios
mdelapenya 173004f
fix: wrong merge conflicts resolution
mdelapenya cb57360
chore: support passing environment when running a command in a container
mdelapenya 6865e98
chore: run elastic agent commands passing an env
mdelapenya 6d60a6d
WIP
mdelapenya 04c7fc8
Merge branch 'master' into 438-fleet-server-scenarios
mdelapenya e5ed65c
chore: separate bootstrapping an agent from connecting to a fleet ser…
mdelapenya 09e4325
fix: use proper fleet-server flags
mdelapenya 491eb17
Merge branch 'master' into 438-fleet-server-scenarios
adam-stokes a557f88
Merge branch 'master' into 438-fleet-server-scenarios
adam-stokes File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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 | ||
mdelapenya marked this conversation as resolved.
Show resolved
Hide resolved
|
||
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.
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.
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.
You might need
xpack.fleet.agents.fleet_server.hosts: [http://?:5601]
instead here with the most recent builds. Probably worth rerunning.