Changed logger.info to logger.debug where the logs include data from and to SFDC
REASON: this data could contain Personal Identifiable Information returned in queries from SFDC
Added logger.info to Request class to show which function was called.
Issue #, if available: #5
Description of changes:
We found that Logging Level INFO is logging too much information, such as queries responses from SFDC requests, which ideally should be in DEBUG logging levels. The main concern here is that the data being logged contains personally identifiable information. Moving the request and response data to a DEBUG log level will allow users to exclude PII from their logs while using INFO and still be able to see what the lambdas are doing. Should help the users that need to be GDPR compliant.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Changed
logger.infotologger.debugwhere the logs include data from and to SFDC REASON: this data could contain Personal Identifiable Information returned in queries from SFDC Added logger.info to Request class to show which function was called.Issue #, if available: #5
Description of changes:
We found that Logging Level
INFOis logging too much information, such as queries responses from SFDC requests, which ideally should be in DEBUG logging levels. The main concern here is that the data being logged contains personally identifiable information. Moving the request and response data to aDEBUGlog level will allow users to exclude PII from their logs while usingINFOand still be able to see what the lambdas are doing. Should help the users that need to be GDPR compliant.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.