You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current getting-started.md of many extensions contains the list of available env vars and config flags. This is a maintenance burden.
We should move the configuration to a dedicated configuration.md which explains which config file is read, and which precedence env vars and cli flags have. We can also link to the bug in viper that prevents cli flags from being used properly with nested structs.
The getting-started.md should be used to describe how to get the extension up and running and how it can be tested. For ocis-glauth I would eg. add an ldapsearch query.
The text was updated successfully, but these errors were encountered:
The current getting-started.md of many extensions contains the list of available env vars and config flags. This is a maintenance burden.
We should move the configuration to a dedicated configuration.md which explains which config file is read, and which precedence env vars and cli flags have. We can also link to the bug in viper that prevents cli flags from being used properly with nested structs.
The getting-started.md should be used to describe how to get the extension up and running and how it can be tested. For ocis-glauth I would eg. add an ldapsearch query.
The text was updated successfully, but these errors were encountered: