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

[FEATURE REQUEST] Use of alternative "remotes" instead of service accounts #132

Open
bonny1992 opened this issue Jul 8, 2024 · 0 comments

Comments

@bonny1992
Copy link

Describe the problem
Since now service accounts cannot be used to get more upload quota, we can use other users in the organizations instead.
We could just create more syncers and uploaders but it'd mean a lot of Nothing to transfer after maybe a long series of checks.

Describe any solutions you think might work
In the syncer and uploader parts we could get an alternative field where we put the "alternative" remotes and if cloudplow doesn't detect an error, it will just cycle to the next syncer or uploader. Instead, if it recognizes an error, it will just proceed switching to the alternative.

...
"remotes": {
   "td-user1-test": ...
   "td-user2-test": ...
}
"syncer": {
  "sync-td-test": {
      ...
      "sync_from" : "td-user1-test",
      "alternatives": { "td-user2-test" }
}

Additional context
Ask away if more is needed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant