Value Statement

When smoketesting our code before handing it over to QE, we frequently run into scenarios that are difficult to test properly without creating a custom OLM bundle and Catalog Source. Being able to thoroughly document and record this process and show that it works will make continuous development a significantly simpler and more robust process in the future.

Definition of Done for Engineering Story Owner (Checklist)

• Document outlining the bundle and catalog source creation process
• Live Demo of the content covered in the document

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.