Change snapshot testing version to 7.9.0-SNAPSHOT

[ruflin]

Currently for development the 8.0.0-SNAPSHOT builds are used but the packages that we develop are shipped for 7.9. It is possible that a feature in 8.0 does not exist in 7.9 but we use it in a package. Because of this I think it makes more sense to develop against the version we plan to ship the packages to. This also ties into elastic/package-storage#163

A follow up discussion should happen on what happens after 7.9 is released. Should we develop against 7.9 or 7.10.0-SNAPSHOT?

[ruflin]

@mtojek Let me know what you think. Probably also others could chime in like @exekias @ycombinator to see if this is a good change or not.

Lets see if CI likes it.

[elasticmachine]

💚 Build Succeeded

Expand to view the summary

Build stats

• Build Cause: [Pull request #202 updated]

• Start Time: 2020-07-28T15:02:35.085+0000

• Duration: 3 min 31 sec

[mtojek]

1. I assume that the same image version will be used by package-registry, package-storage during integration tests?

2. Did you try to use these images? Did it work?

[ruflin]

I did test install a few packages but I realised I did not test installing agents. The agent.yml was not up-to-date. Strangely agents don't show up, need to investigate further why and if it works on master.

For the changes on package-storage, the discussion is here: elastic/package-storage#163 Agree that also version on the package-registry for testing should be adjusted.

[ruflin]

@mtojek Does enrolling agents for you still work with the commands in the README on master?

[mtojek]

It doesn't because of latest changes in Agent:

elastic-agent_1     | 4c520b1e-09f6-479a-8530-bb9ea44f754f
elastic-agent_1     |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
elastic-agent_1     |                                  Dload  Upload   Total   Spent    Left  Speed
100   339  100   339    0     0  14246      0 --:--:-- --:--:-- --:--:-- 14739
elastic-agent_1     | TEZ3R21uTUJQeTFoanNKSFlPc2Q6WkRhRnBuU3FRbDI4MGVoMkhwTWR6dw==
elastic-agent_1     | The Elastic Agent is currently in BETA and should not be used in production
elastic-agent_1     | Error: connection to Kibana is insecure, strongly recommended to use a secure connection (override with --insecure)
environments_elastic-agent_1 exited with code 1

The enrollment script must be updated.

[ruflin]

@mtojek Could you take care of fixing the enrollment script? Do devs use it for development?

[mtojek]

@mtojek Could you take care of fixing the enrollment script? Do devs use it for development?

This is part of the Elastic Agent, part of Docker image. I can open an issue for Ingest Management in Beats.

Devs used to work with standalone instances as it's easier to develop without additional namespaces. Most likely we'll heavily use the containerized Agent in elastic-package test.

[ruflin]

@mtojek Got it. @michalpristas for awareness.

Should we get this PR in without this changes as it is also broken in master? What I tried on my end is installing some packages which worked but not much more. At the same time if this 7.9 does not work, we probably have a problem. CI also passed.

[mtojek]

As the issue with agent is unrelated to your changes, I suppose we can merge this PR. Actually it's good you found the issue with enrollment.

PR approved.

[ruflin]

Thanks. BTW an other issue I found that it should be probably docker-compose -f snapshot.yml -f agent.yml pull to make sure always have the most recent agent image?