PRDE - Story default text according to the team DoR (Definition of Ready)

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):

@Geny Isam Hamud Herrera
02 - STORY BRIEFING (AS A < PERSONA >, I [WANT TO] < NEED >, [SO THAT] < GOAL >):

SRE complained about AI_Process starting “high resource” machines just to failed when pulling image from Docker.

03 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):

IMPACT: High resources machines failing and restarting consuming resource ($cost) just to fail.

As root cause we have a scenario getting impacted by Docker Image Name/Tag that does not exist.

The Dev User uploads a new manifest, sometimes this manifest points to a new docker image because he wants to build a new docker image. When the Dev User runs the Carol App Process, it tries to start a Carol App Process (batch/online) pointing to a Docker Image Name/Tag that does not exist.

04 - GOAL (DESCRIBE THE PROPOSED SOLUTION):

Validate the Docker image even before we send the request to Operator.

Validate what other flows could take advantage of that.

05 - WHO CAN USE THIS FEATURE (USER ROLES):
06 - ACTIVITY DIAGRAM (ACTIVITY DIAGRAM LINK AND IMAGE):
07 - STEPS (ACTIONS TO BE PERFORMED LINKING TO SCREENSHOTS):
08 - ALTERNATIVE STEPS:
09 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
10 - ACCEPTANCE CRITERIA:

• Validate the GitHub configuration on the manifest file when Building Docker Image
• Validate the Docker image exists on our Docker Registry before we send the request to Operator (on the task itself).