-
Notifications
You must be signed in to change notification settings - Fork 94
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
Modify specs files to deploy the 'wazuh-keystore' tool #2791
Labels
Comments
9 tasks
tdrauncieal
added a commit
that referenced
this issue
Jan 29, 2024
tdrauncieal
added a commit
that referenced
this issue
Jan 30, 2024
tdrauncieal
added a commit
that referenced
this issue
Jan 30, 2024
tdrauncieal
added a commit
that referenced
this issue
Jan 30, 2024
tdrauncieal
added a commit
that referenced
this issue
Jan 31, 2024
tdrauncieal
added a commit
that referenced
this issue
Jan 31, 2024
30 tasks
tdrauncieal
added a commit
that referenced
this issue
Jan 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
This issue involves modifying the installation specifications for both RPM and DEB packages in the wazuh-packages repository. The objective is to include the installation of the
wazuh-keystore
tool, which will be located in thebin
directory. This tool is essential for managing the keystore within the Wazuh environment.This issue is related to #2168 which complies with the necessary changes in https://github.com/wazuh/wazuh/
Changes Required
The following changes are necessary to achieve this:
Update the RPM installation spec file to include the
wazuh-keystore
tool in the installation process.Update the DEB installation to include the
wazuh-keystore
tool in the installation process.Ensure that the
wazuh-keystore
tool is correctly placed in thebin
directory during the installation.Definition of Done
wazuh-keystore
tool.wazuh-keystore
tool.wazuh-keystore
tool is correctly placed in thebin
directory during installation.The text was updated successfully, but these errors were encountered: