Audit PubSub publisher on Service Factory

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):

@Geny Isam Hamud Herrera
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?):

Today we create a new Publisher for every message. We need to user the Design Pattern Factory to help on that
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:

  • Change the architecture of our Audit PubSub publisher to be instantiated correctly;
  • Allow all stagings to send data to our Audit PubSub;
  • Use a parameter on YAML to active this feature (intake.yml, intake_docker.yml, mdm.yml, and mdm-docker.yml)
  • Only insert payload on the LANDING step;
  • WARNING: Check how these process will run on SANDBOX, LOCAL, and PRODUCTION(maybe configuration for topic?)
  • Update Notion documentation.