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

[FR] Update existing release process for removed file system rules #2386

Closed
4 tasks done
Tracked by #174166
terrancedejesus opened this issue Nov 2, 2022 · 2 comments
Closed
4 tasks done
Tracked by #174166
Assignees
Labels
backlog enhancement New feature or request python Internal python for the repository v8.7.0

Comments

@terrancedejesus
Copy link
Contributor

terrancedejesus commented Nov 2, 2022

Reference - elastic/kibana#139926

To align with the updated Kibana process of pulling and managing detection rules, TRaDE will need to update tools and documentation for the release process. Below are tasks that should be accomplished prior to FF of 8.7 release.

Tasks:

  • Adjust documentation process
    • Prior to locking, use integrations-pr to create a snapshot package of current ruleset
    • Create Kibana PR to update fleet_packages.json
    • If Kibana CI checks pass, promote package to production
    • Release distribution package via Jenkins
    • Merge Kibana PR
  • Build PoC figma diagram for new release process
  • Revisit kibana-pr CLI command for releasing
    • We need to ensure the command references the local stack version and adjusts the fleet_packages.json file for the PR
  • Potentially remove Kibana detection rules docs and leave package docs

Notes:

  • E2E testing will occur when the Kibana PR is opened with suggested changes to fleet_packages.json
  • Kibana will pull from Snapshot -> Staging -> Production when referencing fleet_packages.json therefore it will pull the snapshot image for dev
  • This process is not supported for 7.x series
@botelastic
Copy link

botelastic bot commented Jan 2, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added the stale 60 days of inactivity label Jan 2, 2023
@botelastic botelastic bot removed the stale 60 days of inactivity label Jan 2, 2023
@terrancedejesus
Copy link
Contributor Author

This can be closed as TRaDE has adjusted our process for releases in which bugs and enhancements were fixed/made to account for this. Additionally, all progress for the release can be tracked via the main issue.
Reference: https://github.com/elastic/ia-trade-team/issues/17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog enhancement New feature or request python Internal python for the repository v8.7.0
Projects
None yet
Development

No branches or pull requests

2 participants