-
Notifications
You must be signed in to change notification settings - Fork 144
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
[FEATURE] Support for service accounts #122
Comments
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
I have created a pull request for service accounts: #123 Install ( reinstall ) test_gupload
How to generate service accounts: https://github.com/Akianonymus/google-drive-upload/tree/wip#generating-service-account-credentials How to use it: https://github.com/Akianonymus/google-drive-upload/tree/wip#for-service-accounts Test and report. |
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
Okay, I'll try and bring the results. |
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
I set up the service account and generated the key and downloaded the .json file. I am informed of it with the syntax -sa it is correct, right? -> test_gupload -sa /root/backup_lapig_gdrive_chave_de_acesso.json folder_name I'm sending the data, but it doesn't appear in my google drive account, I tried to browse the drive but I couldn't find it, when trying to access the link that generates access after going up, he asks to request access to the owner, I'm confused |
The crazy thing is that the file went up and generated an access link, but when I access it asks to request access and I can't find it on my drive. |
If I go up without using the -sa syntax it appears on my drive and the access link works. |
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid
So, i did some work on this today. Almost everything is working now. About the files not appearing, well it's uploaded in the bot account so not accessible. For that, use --share flag. Now, to upload directly in your own account, you have to use the --rootdir option.
Now, just upload using the -sa flag and use --rootdir "root dir id" to upload directly in your account. One problem here is that the files owner will be the service account. To change the owner, i will soon introduce a flag. |
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid * add a seperate service account guide on how to affectively use these service accounts properly
* Add guide in readme on how to generate * Add -sa/--service-account flag * access tokens created by sa will be saved in config, when the sa is given, then it will try to reuse the access token if valid * add a seperate service account guide on how to affectively use these service accounts properly
Was this feature ever merged into master? |
Reference: https://cloud.google.com/iam/docs/service-accounts
To upload more than 750gb per day.
The text was updated successfully, but these errors were encountered: