Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wazuh indexer fork update #54

Closed
7 tasks done
AlexRuiz7 opened this issue Nov 14, 2023 · 0 comments
Closed
7 tasks done

Wazuh indexer fork update #54

AlexRuiz7 opened this issue Nov 14, 2023 · 0 comments
Assignees
Labels
level/epic Epic issue type/enhancement Enhancement issue

Comments

@AlexRuiz7
Copy link
Member

AlexRuiz7 commented Nov 14, 2023

Description

We want to update our wazuh-indexer change-set with the newest changes from the latest releases of Wazuh. Also, we want to be able to generate packages for all the supported tiers, with the new naming schemes and the new artifactory/storage.

We want to generate portable RPM and DEB packages, so all supported Linux distributions share the appropriate package.

We need to generate automated installation and upgrade tests for each supported platform of the generated packages.

Functional requirements

  • All the generated packages include all components, plugins and configurations required to provide a production-ready deployment.
  • All the Wazuh changes to upstream are incorporated by default in all generated packages
  • A developer should be able to generate a package from a given valid Git commit
  • A developer should be able to build packages locally
  • A developer should be able to generate package types individually (tgz, rpm, deb, docker)
  • A developer should be able to generate all packages in one go

Non-functional requirements

  • We maintain the branch structure of Wazuh, renaming the branches when needed to be coherent with the global process
  • We will use GitHub actions to automate the package generation and its testing
  • Only authorized users should be able to execute the package generation pipelines
  • We should use the Wazuh naming convention for development packages
  • All processes must be documented in step-by-step guides, easy to follow by anyone within the repository

Implementation restrictions

  • We must use upstream tests to ensure our changes do not break upstream features
  • We must implement our own installation and upgrade tests for all our supported platforms and operating systems
  • We can explore https://github.com/nektos/act to execute GitHub actions locally

Plan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/epic Epic issue type/enhancement Enhancement issue
Projects
No open projects
Status: Done
Development

No branches or pull requests

1 participant