sa-drive uses service accounts and utilise the Google Cloud Console, and Google APIs. Abuse of this feature is not the aim of sa-drive and we do NOT recommend that you make a lot of projects, just one project and 100 sa will give you 1.4TB of storage which is sufficient.
Only one, Python. Get it from Python.org
Yes It is safe to use sa-drive.
No it would not get your account banned. But if you host any copyrighted content the google might take the content down.
Its also possible that overabuse os the Service Accounts might get your cloud-projects banned by google.
This is best answered by google itself
Ideally you should but you might get ssl errors when creating service accounts using Service Account Utility or when running the sa-drive, the database might give ssl errors.
Hence it is recommened to switch off the vpn.
Again, if you do not abuse the service accounts feature then your personal gmail would be fine. But I'd still recommend a alternate Gmail account which dyou do not use for any personal or official business.
No you are free to choose the root folder (parent folder) name as well as the google group name.
You can have any number of service accounts you want. 100 is given because when adding the service account emails to the google group, a user has the limit of adding 100 members (or emails) per day.
I ran the program to create the service accounts in Service Account Utility but it gave an error. If I run the program again, would it create another 100 service accounts?
The program shows the step by step logs of what its doing. If you get an error, and you are aware that 100 service accounts have already been created then you can open up any text editor and edit the sa_creation_utility.py file and comment out the lines which indicate that accounts are being created. Then re-run the program to create service accounts.
Not at all. Google Could Console is meant to be used by the users, to make their lives easier lol.
Nope. You can log out from the gmail account and still use the sa-drive.
Nope. Everything is built by the user after all. Your information is within your hands (and google's ofcourse)
Not an issue. Because sa-drive will consider only that folder as the parent folder which you add in the _config.py. [Don't forget to rename the file to config.py]
Not at all. The sa-drive utilises the drive space of each service account, and doesn't handle anything in your personal drive
- Simply make another project in google cloud console
- then enable just the google drive api and iam service management api in that project.
- no need to create consent screen , credentials or all that stuff
- then run the service account utitlity with the previous credentials [which you would have got when you'd have made the service accounts for the first time.]
- while choosing the project to create service accounts in, choose the newly created projectId in step 1.
- Add the emails of those new service accounts to the google group
- rename the account files in increasing order. Like if you already have 0-99 .json, rename the new ones from 100-199 .json.
- Copy those 100-199 .json files and paste it into the accounts folder.
Thats all.
That is because the files are not actually being starred in Google Drive. The starred files are visible in the sa-drive ui only.
I can make the files to be starred in google drive, but that would require additional setting up to do. Kindly make an issue on github if you wish to have this feature.
SA index indicates the filename of the service account.json file in the accounts folder.
You cannot. Only option is to disconned the sa-drive
- Delete the uploaded files [optional]
- Delete the service accounts from the project hompage in google cloud console [this should delete the files as well assuming they are not
shared with everyone
] - Delete the google could project where your service accounts are made.
Nope. The program will automatically give the error of storagequotaexceeded.