[Fleet] Fake agent in fleet server standalone

[nchaulet]

Description

Resolve #2605

This create a fake agent id and version for fleet server standalone to allow the coordinator to work.

How to test?

Run a standalone Fleet server and verify that you can enroll an agent and the agent is fully functional (get the policy ...)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-05-24T12:48:36.270+0000

• Duration: 26 min 29 sec

Test stats 🧪

Test	Results
Failed	0
Passed	277
Skipped	1
Total	278

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[joshdover]

How hard would it be to disable the coordinator completely? It does not serve any function right now and will actually incur costs for us due to extra refreshes and the associated API calls on stateless.

[nchaulet]

How hard would it be to disable the coordinator completely? It does serve any function right now and will actually incur costs for us due to extra refreshes and the associated API calls on stateless.

Yes it's probably a better solution long term to remove the coordinator, @michel-laterman we do not have plan to use it? I remember you talking about maybe using this for remote ES output

[michel-laterman]

note that tests are failing due to an issue with the docker v24.0.0 release

[michel-laterman]

I don't think we'll need the coordinator for remote outputs, we've decided to revoke an agent's remote output key on checkin.

[joshdover]

I'm ok with this change to unblock testing, but we should open an issue that is prioritized in the near-future to remove the coordinator.

Needs tests

[michel-laterman]

Have we tested to make sure that the it still grabs the ID that an agent generates if it's running under an agent?

[joshdover]

Have we tested to make sure that the it still grabs the ID that an agent generates if it's running under an agent?

@michel-laterman Improving the unit test and also going to manually test the Agent case right now, but I want to understand more your concern. How would this change be an issue if it's only called when Fleet Server is not in agent mode?