[FEATURE REQUEST] Generate AppConfig spec file from OCClassSettings metadata automatically

[felix-schwarz]

Is your feature request related to a problem? Please describe.
In ownCloud app we have a comprehensive set of settings which can be used for branding, MDM, configuration during development. AppConfig spec files are maintained manually.

When a new setting is added or an existing setting is changed in code, class settings metadata should be used to automatically generate an updated version of the AppConfig spec file.

Describe the solution you'd like
A script, unit test or tool using the OCClassSettings metadata to generate the AppConfig spec XML files automatically.

It should generate different versions with varying degrees of detail/sets of settings based on the status.

RELATED ISSUES

#755 on automatic generation of documentation from metadata.

TASKS

• Research (if needed)
• Create branch feature/feature_name
• Development tasks
  • Implement whatever
  • ...
• Code review and apply changes requested
• Design test plan
• QA
• Merge branch feature/feature_name into master

[michaelstingl]

• Default AppConfig spec file should only contain recommended settings.
• Categories can be used for group feature in spec file

[michaelstingl]

Source data:
https://github.com/owncloud/ios-app/blob/master/doc/CONFIGURATION.json

We already generate docs/modules/ROOT/pages/ios_mdm_tables.adoc
Maybe also move to enterprise/MDM?

Some old specfiles:
https://github.com/owncloud/ios-app/tree/master/enterprise/MDM/AppConfig

Specfiles can be generated manaually:
https://beta.appconfig.jamfresearch.com/spec-creator
(import/edit/export)

Generated specfiles can be used here:
https://beta.appconfig.jamfresearch.com/generator
(import/edit/save as *.plist)

Here's the detailed spec:
https://storage.googleapis.com/appconfig-media/appconfig-content/uploads/2017/01/ManagedAppConfig.pdf

More information:
https://www.appconfig.org/

[michaelstingl]

Parameter should be grouped by categoryTag, displayed as category.

Key is the flatIdentifier

[michaelstingl]

We could use GitHub Actions to run this automatically, similar to the MDM tables.

[mmattel]

Maybe also move to enterprise/MDM

It would be great to have one location (tbd, but not inside the docs folder) for all files which are and will be generated for docs or are docs relevant, so we have a single location for those files.

[michaelstingl]

We already generate docs/modules/ROOT/pages/ios_mdm_tables.adoc
Maybe also move to enterprise/MDM?

Better move to doc/CONFIGURATION.adoc (#1070)