-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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] occ config:app:list, config:system:list #32006
Comments
GitMate.io thinks the contributor most likely able to help you is @PVince81. Possibly related issues are #12530 (Feature Request), #8569 (Feature requests), #15789 (request for occ ldap:list-config command), #3173 ( feature request: confirmation for admin), and #25708 ([Feature Request] ./occ user:logonlist). |
Note that there is:
which lists everything in the "system" config ( But when you enable an app, then it will be using defaults for values that have not been set. e.g. my test system
But there are lots of A command that lists all the possible settings, including those that are currently taking a default value, would be useful. The challenge will be exactly how to "query" an app and have it tell you, or have "registered", all the settings keys and defaults that it uses. |
@mmattel occ app:list gives you the list of installed apps. The keys used in the configs are the app ids, assuming apps aren't cheating. Documenting this in the occ command help could be enough. |
This issue is two fold. The original intend of having a occ command listing app and system data is available with config:list. Did not recognized that. But the config:xxx commands are documented very basic and therefore I created a doc issue as a reminder. On the other hand side, when you want to change a setting, you might use config:list to get infos about but again you struggle because it is not clear which keys are present and changable and what values are allowed/default. Pls see the doc issue and the comment from @phil-davis above for more details. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
We currently have (as of 10.0.8):
But there is no
config:app:list
command (for a given app name provided).This FR would list all config names available for a particular app.
If not possible for all apps, this can be done eg for core and be documented
True in the same way also for
config:system
,config:system:list
How does an admin know which names are available in eg the core app or in system?
This also would relieve documentation needs
@PVince81 @VicDeo
The text was updated successfully, but these errors were encountered: