[feature/settings-metadata] Class Settings Metadata support

[felix-schwarz]

Description

Support for class settings metadata.

Related Issue

owncloud/ios-sdk#71
Refresh of #831 (which wouldn't refresh to the latest branch HEAD)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

QA

Report: #838 (comment)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
4 out of 6 committers have signed the CLA.

✅ dschmidt
✅ hosy
✅ mneuwert
✅ michaelstingl
❌ felix-schwarz
❌ Michael Neuwert

---

Michael Neuwert seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[jesmrec]

QA

The aim of the current PR QA stage is checking how the documentation is generated, not the documentation itself. All entries in the doc will be checked at the time the MDM fields' behaviour is tested.

1) Script execution

execution of generate_docs.sh finishes with TEST SUCCEEDED

no problems detected during the execution

2) JSON file

The JSON file generated by the script is correctly shaped. Every object contains several fields and meta-fields (do not appear in the final document, but probably needed somehow). It'd be interesting to write somewhere (adoc file, documentation or wherever), about it, so that the reader/system admin/whoever can understand correctly what do they mean.

3) adoc file

This is the product of the script. With testing purposes, i've rendered it to html5 by using the asciidoctor (just for an easier visualization and comparison)

Document is correctly generated, but not with all objects in the JSON file (this was already reported in the chats). The missing objects are:

• connection-allowed-authentication-methods in category Security
• connection.connection-preferred-authentication-methods in category Security
• allow-cellular in category Connection

[michaelstingl]

• connection-allowed-authentication-methods in category Security
• connection.connection-preferred-authentication-methods in category Security
• allow-cellular in category Connection

@dschmidt this 3 doesn't get picked up from gomplate. They're in JSON, but they aren't in the adoc.

[michaelstingl]

@felix-schwarz @mneuwert can we merge this? What's left? Open new issue for the remaining tasks?

[felix-schwarz]

@michaelstingl As last addition, I added the space-less categoryTags and merged the PR. The adoc generation issue is still open and now tracked in #854.

[mneuwert]

@felix-schwarz After merging your changes into feature/mdm_enhancements and while generating docs with antora I get following warnings:

asciidoctor: WARNING: ios_mdm.adoc: line 37: tag 'actions' not found in include file: modules/ROOT/pages/ios_mdm_tables.adoc
asciidoctor: WARNING: ios_mdm.adoc: line 49: tag 'passcode' not found in include file: modules/ROOT/pages/ios_mdm_tables.adoc
asciidoctor: WARNING: ios_mdm.adoc: line 89: tag 'shortcuts' not found in include file: modules/ROOT/pages/ios_mdm_tables.adoc

So, at least first two have been there before..

[michaelstingl]

Are the tags actions, passcode and shortcuts in the JSON?

[mneuwert]

@michaelstingl I had to regenerate JSON, so please ignore my previous comment.. Shortcuts need some more implementation work and 'display settings' are missing eventually due to problems in template file...

Latest checked in configuration does include actions and passcode at least (in mdm_enhancements branch though)