Epic Goal

Streamline the management of operator bundles and enhance cluster operations by developing a comprehensive suite of automation tools and utilities within the "installer-dev-tools" repository.

Why is this important?

By developing a repo for automation tools and utilities, the team can deliver support tools that will improve the efficiency, reliability, security, code quality, productivity, and scalability of our team's operation.

Scenarios

A team of developers is managing a cluster for a critical application. This cluster uses several operator bundles that need to be regularly updated and synchronized with the latest versions to ensure optimal performance and security.

Acceptance Criteria

• [x] Clean up scripts are developed and functional.
• [x] Operator bundles are automatically synchronized with the latest versions from upstream sources.
• [x] SCC reviews are automated and consistently run upon configuration changes.
• [x] Linting tools are integrated into the development workflow and provide real-time feedback. 
• [x] Scripting library is developed and provides a collection of automation scripts for common operational tasks.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>