I am trying to deploy CLI on AWS Lambda, but the integrated UID check on config folder described here blocks the CLI from running with error "Can't continue. We can't safely access "[CONFIGFOLDER]" because it's not owned by the current user. Change the owner or logged in user and try again."
The user under which is the script running on Lambda is obviously different from the user used for package creation and deployment.
Is there any way to avoid or circumvent this problem?
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided