Story (Required)

As a developer trying to code in the redhat-ai-dev github or I want use a common set of bash libraries for setting up auth and tls certs for github, quay, etc.

Background (Required)

As of the creation of this story, the

• ai-lab-helm-charts,
• ai-lab-template

repositories all have some similar, but at the moment unique/not shared, use of bash for manipulating secrets and configmaps for auth and tls certs

An inventory of this usage can be seen at https://github.com/redhat-ai-dev/dev-ai-bash/tree/main/git/setup-config and https://github.com/redhat-ai-dev/dev-ai-bash/tree/main/buildah-quay https://github.com/redhat-ai-dev/dev-ai-bash/tree/main/k8s/secrets

Out of scope

<Defines what is not included in this story>

Approach (Required)

• Refactor / parameterize the various versions of each of these git related units of work into methods whose invocations could replace the current bash in the repos listed above 
• Leverage the methodologies listed at https://github.com/redhat-ai-dev/dev-ai-bash?tab=readme-ov-file#how-will-we-reuse-this-repo-in-our-higher-level-repos and then replace the current bash in each of the repositories above with calls to our new methods

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Required)

documentation updates (design docs, release notes etc)
demo needed
CI in consuming repositories updated as needed/confirmed as still passing as that CI manifests in each of the consuming repositories

Done Checklist

Code is completed, reviewed, documented and checked in
Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
Continuous Delivery pipeline(s) is able to proceed with new code included
Customer facing documentation, API docs, design docs etc. are produced/updated, reviewed and published
Acceptance criteria are met
If the Grafana dashboard is updated, ensure the corresponding SOP is updated as well