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

[Feature Request] occ config:app:list, config:system:list #32006

Closed
mmattel opened this issue Jul 6, 2018 · 5 comments
Closed

[Feature Request] occ config:app:list, config:system:list #32006

mmattel opened this issue Jul 6, 2018 · 5 comments

Comments

@mmattel
Copy link
Contributor

mmattel commented Jul 6, 2018

We currently have (as of 10.0.8):

      config:app:delete
      config:app:get
      config:app:set
      config:system:delete
      config:system:get
      config:system:set

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

@mmattel mmattel changed the title [Feature Request] occ config:app:list [Feature Request] occ config:app:list, config:system:list Jul 6, 2018
@ownclouders
Copy link
Contributor

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).

@phil-davis
Copy link
Contributor

Note that there is:

config:list

which lists everything in the "system" config (config.php) and the "app" config - key-value pairs that are set for each of the apps. And it takes the app name or system as a parameter, which shows just the relevant section. So I think viewing the actual currently set values is covered.

But when you enable an app, then it will be using defaults for values that have not been set. e.g. my test system files_sharing happens to currently have:

./occ config:list files_sharing
{
    "apps": {
        "files_sharing": {
            "enabled": "yes",
            "incoming_server2server_share_enabled": "no",
            "installed_version": "0.10.1",
            "outgoing_server2server_share_enabled": "no",
            "types": "filesystem"
        }
    }
}

But there are lots of files_sharing options that can be set.

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.

@PVince81
Copy link
Contributor

PVince81 commented Jul 9, 2018

@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.

@mmattel
Copy link
Contributor Author

mmattel commented Jul 9, 2018

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.

@stale
Copy link

stale bot commented Sep 20, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants