-
Notifications
You must be signed in to change notification settings - Fork 187
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
Allow configuring storage registry with envvars #7554
Allow configuring storage registry with envvars #7554
Conversation
Signed-off-by: jkoberg <jkoberg@owncloud.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Martin <github@diemattels.at>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@dragotin once you are familiar with the new envvars, could you improve the description in a follow-up PR? |
JSON string `yaml:"json"` // TODO: configure via env? | ||
Driver string `yaml:"driver" env:"GATEWAY_STORAGE_REGISTRY_DRIVER" desc:"The driver name of the storage registry to use."` | ||
Rules []string `yaml:"rules" env:"GATEWAY_STORAGE_REGISTRY_RULES" desc:"The rules for the storage registry."` | ||
JSON string `yaml:"json" env:"GATEWAY_STORAGE_REGISTRY_CONFIG_JSON" desc:"Additional configuration for the storage registry in json format."` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Q: how does the json get assigned to the variable? Imho a reference to a file would do this.
See: USERS_LDAP_CACERT where we have a default path/file if not otherwise defined: If not defined, the root directory derives from $OCIS_BASE_DATA_PATH:/idm.
Just my 2c.
Allow configuring storage registry with envvars
Allows configuring the storage registry in the gateway service using envvars