Epic Goal

• Compose a decoupled, common, and reusable repository of bash functions that can be consumed by our higher level repositories 

Why is this important?

• Logic duplication is a general no-no
• Common libraries will help build bash in any yet to be created repos under the redhat-ai-dev org
• decoupled and more reusable bash logic could help with our forays into automation 

Scenarios

1. As a developer of function under redhat-ai-dev, I would like to have one repo/place to deal with bash logic commonly used by our existing function, so as to optimize my coding efforts 

Acceptance Criteria (Mandatory)

• integrated with any CI employed by consuming repositories - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
•  

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. The story https://issues.redhat.com/browse/RHDHPAI-197  lead to the creation of this epic

Open questions::

1. Priority of this could depend on a) how much automated conversion items https://issues.redhat.com/browse/RHDHPAI-376 through https://issues.redhat.com/browse/RHDHPAI-379 can benefit from this b) how often do we have to fix the bash sprinkled across our repos once we GA, and we find not having a common bash library negatively impacts completely fixing an issue

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment