Lots of work for ISHLT badge printing.

app/methods/e_impexium_methods.py

@@ -273,6 +273,8 @@ def get_event_registrants(
 
 # ### BEGIN ### API External Impexium Methods ### get_individual_profile() ###
 # Updated 2022-04-22
+# NOTE: Without details the results are very basic. Pretty much just their name.
+# Including details adds the addresses, customFields, emails, memberships, phones, etc
 @logger_reset
 def get_individual_profile(
         individual_id: str,
@@ -309,6 +311,7 @@ def get_individual_profile(
             # log.debug(resp.json())
 
             if resp.status_code == 200:
+                log.info('Status 200')
                 log.debug(resp.json())
 
                 impexium_individual_profile_raw = resp.json() # .get('data').get('dataList')[0]
@@ -319,7 +322,7 @@ def get_individual_profile(
 
                 try_request = False
             elif resp.status_code == 404:
-                log.info('No results returned.')
+                log.info('No results returned (status 404)')
                 try_request = False
                 impexium_individual_profile = None
             elif resp.status_code == 429:
@@ -328,6 +331,7 @@ def get_individual_profile(
                 try_request = True
                 impexium_individual_profile = False
             else:
+                log.info('Not trying again')
                 try_request = False
                 impexium_event_registration_list = False
 

app/methods/event_person_methods.py

@@ -1,11 +1,10 @@
-from __future__ import annotations
 import datetime
 
 from typing import Dict, List, Optional, Set, Union
 from pydantic import BaseModel, EmailStr, Field, PrivateAttr, ValidationError, validator
 
 from app.db_sql import get_account_id_w_for_type_id, redis_lookup_id_random, sql_insert, sql_select, sql_update
-from app.lib_general import log, logging
+from app.lib_general import log, logging, logger_reset
 
 # from app.methods.event_abstract_methods import load_event_abstract_obj
 from app.methods.event_badge_methods import create_update_event_badge_obj_v4, load_event_badge_obj
@@ -25,6 +24,7 @@ from app.models.event_person_models import Event_Person_New_Base, Event_Person_B
 
 
 # ### BEGIN ### API Event Person Methods ### load_event_person_obj() ###
+@logger_reset
 def load_event_person_obj(
         event_person_id: int|str,
         enabled: str = 'enabled', # enabled, disabled, all
@@ -188,6 +188,7 @@ def load_event_person_obj(
 # ### BEGIN ### API Event Person Methods ### get_event_person_rec_list() ###
 # for_obj_type: account, event, event_registration, event_badge, person, user
 # Updated 2021-09-10
+@logger_reset
 def get_event_person_rec_list(
         for_obj_type: str, # NOTE: This is not for_type because the field name generated based
         for_obj_id: str, # NOTE: This is not for_id because the field name generated based
@@ -310,6 +311,7 @@ def get_event_id_w_event_person_id(
 
 # ### BEGIN ### API Event Person Methods ### create_update_event_person_obj_v4() ###
 # Updated 2022-02-23
+@logger_reset
 def create_update_event_person_obj_v4(
         event_person_dict_obj: Event_Person_Base|dict,
         event_person_id: int|str|None = None,
@@ -321,7 +323,7 @@ def create_update_event_person_obj_v4(
         fail_any: bool = False, # Fail if any thing goes wrong for sub objects
         return_outline: bool = False,
         ) -> int|bool:
-    log.setLevel(logging.DEBUG) # DEBUG, INFO, WARNING, ERROR, EXCEPTION, CRITICAL
+    log.setLevel(logging.INFO) # DEBUG, INFO, WARNING, ERROR, EXCEPTION, CRITICAL
     log.debug(locals())
 
     # ### SECTION ### Secondary data validation
@@ -526,6 +528,7 @@ def create_update_event_person_obj_v4(
 # NOTE: Is it a good idea to create and or update a person and or user here??? The create_event_person_obj() below does do that.
 # NOTE NOTE NOTE NOTE: I don't like the idea of creating or updating person and or user here. It just does not seem right... Security risk? Complexity?
 # Updated 2021-08-25
+@logger_reset
 def create_event_person_obj(
     event_id: int|str,
     event_person_obj_new: Event_Person_Base,
@@ -861,6 +864,7 @@ def update_event_person_obj_v3(
 # NOTE NOTE NOTE NOTE: This will be taken over by _exist version
 # NOTE NOTE NOTE NOTE: I don't like the idea of creating or updating person and or user here. It just does not seem right... Security risk? Complexity?
 # Reviewed and updated 2021-08-10
+@logger_reset
 def update_event_person_obj(
         event_person_id: int|str, # Ideally the int ID should be passed. This allows for updating of the id_random value.
         event_person_obj_up: Event_Person_Base,
@@ -1051,4 +1055,4 @@ def smart_event_person_obj(event_person_obj_new:Event_Person_Base) -> int|bool:
 
     log.debug(f'Returning the new event_person_id: {event_person_id}')
     return event_person_id
-# ### END ### API Event Person Methods ### smart_event_person_obj() ###
+# ### END ### API Event Person Methods ### smart_event_person_obj() ###