Update installer code to support deployer abstraction#1163
Update installer code to support deployer abstraction#1163adam-stokes merged 14 commits intomasterfrom
Conversation
Signed-off-by: Adam Stokes <51892+adam-stokes@users.noreply.github.com>
…g into feat-installer-rework
Signed-off-by: Adam Stokes <51892+adam-stokes@users.noreply.github.com>
|
@mdelapenya have a look at this PR as it shows how we can abstract out a 'Package' and support the different installation/configuration methods. This also fixes the installer interface as the previous one wasn't adhering to the interface |
Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
Signed-off-by: Adam Stokes <51892+adam-stokes@users.noreply.github.com>
|
@mdelapenya I needed to rework the installer code to support attaching to a deployment. Similar to the way |
Signed-off-by: Adam Stokes <51892+adam-stokes@users.noreply.github.com>
Signed-off-by: Adam Stokes <51892+adam-stokes@users.noreply.github.com>
Signed-off-by: Adam Stokes <51892+adam-stokes@users.noreply.github.com>
Signed-off-by: Adam Stokes <51892+adam-stokes@users.noreply.github.com>
Signed-off-by: Adam Stokes <51892+adam-stokes@users.noreply.github.com>
mdelapenya
left a comment
There was a problem hiding this comment.
I've verified that Beats PR are covered by this PR, so LGTM
How to test a Beats PR:
# needed to get artifacts from GCP bucket
export BEATS_USE_CI_SNAPSHOTS=true
# git sha1 for a commit in the proper maintenance branch
export GITHUB_CHECK_SHA1=b989478a3003c1b41722b7245586d58d832748a4
SUITE="fleet" TAGS="stand_alone_agent" TIMEOUT_FACTOR=3 LOG_LEVEL=TRACE DEVELOPER_MODE=true \
make -C e2e functional-testThinking about adding this to the PR template ⬆️⬆️
Yea we should add that to the template for sure |
* Installer refactor * More work abstracting out installer bits * Update internal/deploy/docker.go * Update installer to support attaching a deployment * cleanup execing into services * fix e2e tests * print logs of container, up timeout factor * revert jenkinsfile * remove dead code Signed-off-by: Adam Stokes <51892+adam-stokes@users.noreply.github.com> Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com> (cherry picked from commit 584769a)
* Installer refactor * More work abstracting out installer bits * Update internal/deploy/docker.go * Update installer to support attaching a deployment * cleanup execing into services * fix e2e tests * print logs of container, up timeout factor * revert jenkinsfile * remove dead code Signed-off-by: Adam Stokes <51892+adam-stokes@users.noreply.github.com> Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com> (cherry picked from commit 584769a) # Conflicts: # e2e/_suites/fleet/fleet.go # internal/installer/base.go # internal/installer/deb.go # internal/installer/rpm.go # internal/installer/tar.go
* master: Update installer code to support deployer abstraction (elastic#1163)
* Installer refactor * More work abstracting out installer bits * Update internal/deploy/docker.go * Update installer to support attaching a deployment * cleanup execing into services * fix e2e tests * print logs of container, up timeout factor * revert jenkinsfile * remove dead code Signed-off-by: Adam Stokes <51892+adam-stokes@users.noreply.github.com> Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com> (cherry picked from commit 584769a) Co-authored-by: Adam Stokes <51892+adam-stokes@users.noreply.github.com>
…c#1163) (elastic#1198)" This reverts commit d5689c7.
* master: Revert "Update installer code to support deployer abstraction (elastic#1163)" (elastic#1201) Update installer code to support deployer abstraction (elastic#1163)
What does this PR do?
Refactors the installer code to utilize the deployment backend mechanics
Why is it important?
This allows us to greatly increase the support of testing against various deployments (local host only, docker, kubernetes) and abstracts out the code necessary to install and run the elastic-agent on those providers
Checklist
make noticein the proper directory)