Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Emulation Tuning] Adjust Access Stored Keys and Tokens in Drive Emulation #75

Merged
merged 2 commits into from
Aug 31, 2023

Conversation

terrancedejesus
Copy link
Collaborator

@terrancedejesus terrancedejesus commented Aug 31, 2023

Overview

This pull request makes adjustments to the Access Stored Keys and Tokens in Drive emulation.

  • Removes the file extension list splicing so all file extensions are used. Originally this was added to set a limit to reduce time taken for emulation
  • added description and references attributes to Emulation class
  • added error handling to all methods
  • removed access requests and file downloads from Selenium and Chrome to requests with sessions
  • files are now downloaded to swat/etc/artifacts/ after being staged

emulation log file: collection_drive_access_private_keys.log
note that these "private key" files are empty and the URLs are NULL including the folder ID within Google Workspace.

Screenshot 2023-08-31 at 10 47 48 AM

@terrancedejesus terrancedejesus merged commit ad7d21c into main Aug 31, 2023
2 checks passed
@terrancedejesus terrancedejesus changed the title [Emulation Tuning] Adjust 'Access Stored Keys and Tokens in Drive' Emulation [Emulation Tuning] Adjust Access Stored Keys and Tokens in Drive Emulation Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant