nick/753-Data-Sync
1
0
Fork 0
Code Issues 4 Pull Requests Releases 2 Activity

Enhancement: Add debug logging and conditional page file saving #2

New Issue
Closed
opened 2025-03-26 12:23:41 -04:00 by nick · 1 comment
nick commented 2025-03-26 12:23:41 -04:00
Owner
Copy Link

Enhancement Proposal

The current version of the 753DataSync script does not have the ability to enable detailed debug-level logging. We would like to enhance the script to add debug logging, and also to allow saving the individual page data files (e.g., enforcement_page_x_) only when debug logging is enabled. The aggregated data file should still be saved with the info logging level.

Expected Behavior:

  • The script should log at the debug level, allowing detailed logs to be visible when debugging is enabled.
  • The individual page data files (e.g., enforcement_page_x_) should only be saved if the logging level is set to debug.
  • The aggregated data file should always be saved with the info logging level, even when debug logging is disabled.

Acceptance Criteria:

  • Add support for setting the logging level dynamically (via environment variable or script argument).
  • Only save the individual page files if the logging level is set to debug.
  • Always save the aggregated data file with the info logging level.
  • Update the documentation to reflect these changes.
## Enhancement Proposal The current version of the `753DataSync` script does not have the ability to enable detailed debug-level logging. We would like to enhance the script to add debug logging, and also to allow saving the individual page data files (e.g., `enforcement_page_x_`) only when debug logging is enabled. The aggregated data file should still be saved with the info logging level. ## Expected Behavior: - The script should log at the debug level, allowing detailed logs to be visible when debugging is enabled. - The individual page data files (e.g., `enforcement_page_x_`) should only be saved if the logging level is set to debug. - The aggregated data file should always be saved with the info logging level, even when debug logging is disabled. ## Acceptance Criteria: - Add support for setting the logging level dynamically (via environment variable or script argument). - Only save the individual page files if the logging level is set to debug. - Always save the aggregated data file with the info logging level. - Update the documentation to reflect these changes.
nick added the
enhancement
 label 2025-03-26 12:35:51 -04:00
nick self-assigned this 2025-03-26 12:36:23 -04:00
nick added reference refs/tags/v2025.04 2025-04-01 20:05:05 -04:00
nick commented 2025-04-01 20:06:18 -04:00
Author
Owner
Copy Link

This enhancement is now complete and ready for closure.

This enhancement is now complete and ready for closure.
nick closed this issue 2025-04-01 20:06:19 -04:00
Sign in to join this conversation.
v2025.04
Branches Tags
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
nick
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: nick/753-Data-Sync#2
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?