-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
feat: move primary object store configuration to a single place #52816
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
Conversation
da651df to
56169fd
Compare
56169fd to
2c98eea
Compare
3ee53a3 to
3567dd1
Compare
Signed-off-by: Robin Appelman <[email protected]>
3567dd1 to
7599162
Compare
|
/backport to stable31 |
|
/backport to stable30 |
|
The backport to # Switch to the target branch and update it
git checkout stable31
git pull origin stable31
# Create the new backport branch
git checkout -b backport/52816/stable31
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 7599162c
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/52816/stable31Error: Failed to push branch backport/52816/stable31: remote: {"auth_status":"auth_error","body":"Invalid username or token. Password authentication is not supported for Git operations."} Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
Extracted from #52786 to get smaller, easier to review PRs
Extracts and unifies the handling of primary object store configuration.
As with #52786, this also allows configuring multibucket object storages by settings the
multibucketarguments instead of having the configuration under the theobjectstore_multibucketkey. (it should have never be done like that tbh)