BQ: consider the status READY_WITH_LOAD_ERROR as PROVISIONED
Description
PRDE - Story default text according to the team DoR (Definition of Ready)
01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
02 - STORY BRIEFING (AS A < PERSONA >, I [WANT TO] < NEED >, [SO THAT] < GOAL >):
03 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
Consider the status READY_WITH_LOAD_ERROR as provisioned.
The down-side of the status READY_WITH_LOAD_ERROR is that a few tables will have error on the field mdmBigQuerySynchronizationStatus
(possible FAILED_TO_SYNC).
04 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
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:
- Consider tenants with the mdmBigQueryStatusType as READY_WITH_LOAD_ERROR with same behavior as READY
- Areas getting impacted today:
- Tenants status on org admin (it shows as not provisioned)
- When I open a staging table it says BQ isn’t provisioned.