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

Update package generation tools #156

Closed
1 task done
Tostti opened this issue Mar 20, 2024 · 0 comments · Fixed by #157
Closed
1 task done

Update package generation tools #156

Tostti opened this issue Mar 20, 2024 · 0 comments · Fixed by #157
Assignees
Labels
level/task Task issue request/operational Operational request type/enhancement New feature or request

Comments

@Tostti
Copy link
Member

Tostti commented Mar 20, 2024

In the context of the packages redesign project, new requirements have been defined or have changed slightly, so we need to update our tools to accomplish with these requirements, which in our case are:

  • Distinction between development and production packages. The GH workflow must provide a way to switch between the generation of these 2 packages types.
  • Production packages follow a different naming convention, which corresponds to current packages naming (see wazuh-dashboard packages list). Production packages do not contain the commit's SHA.
  • By default, all packages use 0 as revision, unless stated otherwise. This means that the GH Workflow should allow providing the revision number as input.
  • The GH Workflow must always write the package into the S3 bucket, and overwrite any existing package with the same name.

For a complete list of requirements, refer to https://github.com/wazuh/internal-devel-requests/issues/187.

PR

@Tostti Tostti self-assigned this Mar 20, 2024
@wazuhci wazuhci moved this to In progress in Release 4.9.0 Mar 20, 2024
@Tostti Tostti linked a pull request Mar 20, 2024 that will close this issue
7 tasks
@asteriscos asteriscos added type/enhancement New feature or request level/task Task issue request/operational Operational request labels Mar 25, 2024
@Tostti Tostti moved this from In progress to Pending review in Release 4.9.0 Apr 4, 2024
@wazuhci wazuhci moved this from Pending review to Done in Release 4.9.0 Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue request/operational Operational request type/enhancement New feature or request
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants