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

settings service: storage-system configuration #4058

Closed
wkloucek opened this issue Jun 29, 2022 · 3 comments
Closed

settings service: storage-system configuration #4058

wkloucek opened this issue Jun 29, 2022 · 3 comments

Comments

@wkloucek
Copy link
Contributor

wkloucek commented Jun 29, 2022

Describe the bug

When I want to configure the setting service to use the storage-system service as a backend and they do not run on the same machine (same localhost), I cannot use default values and need to change following values:

STORAGE_GATEWAY_GRPC_ADDR and STORAGE_GRPC_ADDR both need to point to the GRPC endpoint of the storage-system service.

Expected behavior

There is one setting that needs to be pointed to the GRPC endpoint of the storage-system service.

The environment variable to do so starts with SETTINGS_ and has a similar naming as other services that use the storage-system, eg: SHARING_USER_CS3_PROVIDER_ADDR

Actual behavior

There are two values that I need to configure. Both start with STORAGE_

@micbar
Copy link
Contributor

micbar commented Sep 14, 2022

@wkloucek Is this a GA release blocker?

@micbar micbar modified the milestones: 2.0.0 General Availability, 2.1.0 Service Pack 1 Sep 14, 2022
@wkloucek
Copy link
Contributor Author

@wkloucek Is this a GA release blocker?

No I don't thinks so. Just a configuration quirk

@wkloucek
Copy link
Contributor Author

the user facing configuration quirk is fixed with the switch to service names in 3.1.0-next.1, but the duplicated default value still persists:

GatewayAddress: "com.owncloud.api.storage-system",
StorageAddress: "com.owncloud.api.storage-system",

@github-project-automation github-project-automation bot moved this from Prio 3 or less to Done in Infinite Scale Team Board Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants