This repository has been archived by the owner on Sep 21, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17
Allow running the shipper in standalone mode independently of the agent #83
Closed
Labels
Comments
cmacknz
added
Team:Elastic-Agent-Data-Plane
Label for the Agent Data Plane team
v8.5.0
labels
Jul 21, 2022
cmacknz
changed the title
Allow running the shipper independently of the agent
Allow running the shipper in standalone mode independently of the agent
Jul 21, 2022
Closed
2 tasks
It's currently possible to run the shipper server using the controller mock like so: elastic-agent-shipper/controller/controller_client_test.go Lines 34 to 91 in 34571c4
We're planning to automate this but for the time being it can be coded quickly for debugging. |
29 tasks
For now it's going to be implemented as a flag that uses a configuration file bypassing the control protocol altogether. This will enable us to run integration tests without running the actual agent. However, there is this agent mock tool being developed that will allow us to include the control protocol implementation in our integration tests as well. The flag is rather a temporary solution. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The shipper's default mode of operation is to expect to be started by the agent, expecting to be passed the address of the agent control protocol server to connect to. The control protocol is then responsible for sending the shipper it's runtime configuration.
To make local development and testing easier, allow the shipper to run in a standalone mode independent of the agent. Add a new command line flag that causes the shipper to read its configuration file from disk and start without waiting to connect to the agent control protocol server.
The text was updated successfully, but these errors were encountered: