feat: implement the installation of the agent

.ci/.e2e-tests.yaml

@@ -8,6 +8,8 @@ SUITES:
     feature: "metricbeat"
   - suite: "ingest-manager"
     feature: "stand_alone_mode"
+  - suite: "ingest-manager"
+    feature: "fleet_mode"
   - suite: "metricbeat"
     feature: "apache"
   - suite: "metricbeat"

cli/config/compose/services/centos/docker-compose.yml

@@ -0,0 +1,6 @@
+version: '2.3'
+services:
+  centos:
+    image: centos:${centosTag:-7}
+    container_name: ${centosContainerName} 
+    entrypoint: tail -f /dev/null

cli/docker/docker.go

@@ -3,6 +3,7 @@ package docker
 import (
 	"bytes"
 	"context"
+	"strings"
 
 	"github.com/docker/docker/api/types"
 	"github.com/docker/docker/api/types/filters"
@@ -92,10 +93,11 @@ func ExecCommandIntoContainer(ctx context.Context, containerName string, user st
 		"container": containerName,
 		"command":   cmd,
 		"detach":    detach,
-		"output":    output,
 		"tty":       tty,
 	}).Debug("Command sucessfully executed in container")
 
+	output = strings.ReplaceAll(output, "\n", "")
+
 	return output, nil
 }
 

e2e/_suites/ingest-manager/configurations/kibana.config.yml

@@ -7,6 +7,8 @@ elasticsearch.username: elastic
 elasticsearch.password: changeme
 xpack.monitoring.ui.container.elasticsearch.enabled: true
 
+xpack.encryptedSavedObjects.encryptionKey: "12345678901234567890123456789012"
+
 xpack.ingestManager.enabled: true
 xpack.ingestManager.epm.enabled: true
 xpack.ingestManager.epm.registryUrl: http://package-registry:8080

e2e/_suites/ingest-manager/features/fleet_mode_agent.feature

@@ -4,24 +4,22 @@ Feature: Fleet Mode Agent
 
 @enroll
 Scenario: Deploying an agent
-  Given the "Fleet" Kibana setup has been executed
   When an agent is deployed to Fleet
   Then the agent is listed in Fleet as online
     And system package dashboards are listed in Fleet
-    And there is data in the index
 
 @start-agent
 Scenario: Starting the agent starts backend processes
   When an agent is deployed to Fleet
-  Then the "filebeat" process is "started" on the host
-    And the "metricbeat" process is "started" on the host
+  Then the "filebeat" process is in the "started" state on the host
+    And the "metricbeat" process is in the "started" state on the host
 
 @stop-agent
 Scenario: Stopping the agent stops backend processes
   Given an agent is deployed to Fleet
-  When the "agent" process is "stopped" on the host
-  Then the "filebeat" process is "stopped" on the host
-    And the "metricbeat" process is "stopped" on the host
+  When the "elastic-agent" process is "stopped" on the host
+  Then the "filebeat" process is in the "stopped" state on the host
+    And the "metricbeat" process is in the "stopped" state on the host
 
 @unenroll
 Scenario: Un-enrolling an agent
@@ -34,11 +32,10 @@ Scenario: Un-enrolling an agent
 Scenario: Re-enrolling an agent
   Given an agent is deployed to Fleet
     And the agent is un-enrolled
-    And the "agent" process is "stopped" on the host
+    And the "elastic-agent" process is "stopped" on the host
   When the agent is re-enrolled on the host
-    And the "agent" process is "started" on the host
+    And the "elastic-agent" process is "started" on the host
   Then the agent is listed in Fleet as online
-    And there is data in the index
 
 @revoke-token
 Scenario: Revoking the enrollment token for an agent

e2e/_suites/ingest-manager/features/ingest_manager.feature

@@ -7,8 +7,8 @@ Feature: Stand-alone Agent Mode
 @start-agent
 Scenario: Starting the agent starts backend processes
   Given a stand-alone agent is deployed
-  Then the "filebeat" process is "started" on the host
-    And the "metricbeat" process is "started" on the host
+  Then the "filebeat" process is in the "started" state on the host
+    And the "metricbeat" process is in the "started" state on the host
 
 @deploy-stand-alone
 Scenario: Deploying a stand-alone agent