Univention Bugzilla – Bug 43838
App Setting: Run configure script
Last modified: 2017-06-28 15:55:04 CEST
After setting are applied, a Script should be run. myapp.configure Default is No Script, i.e. no execution, even for appbox. No arguments except --app myapp --app-version 1.0 --error-file /tmp/XXX The script shall apply settings saved earlier. By parsing base.conf manually. Thus, settings have to be stored independently from configure. Exiting with an error shall not abort the App Center. +++ This bug was initially created as a clone of Bug #43816 +++ Goal is to allow Apps to specify custom setting that are then applied inside the container / on the host. Specification is done via a new file: myapp.settings with is dritten in ini format: [my/setting] ... [my/second/setting] ...
*** Bug 42839 has been marked as a duplicate of this bug. ***
A configure script has been added in univention-appcenter (5.0.23-69) It is called at the end of univention-app configure which is also part of univention-app install. I have also added a test case for this bug. But I did not get to pass. In my manual tests, the feature works, though. Maybe you can have a look. After successful QA, please clone to 4.2-0-errata. BTW: univention-app shell $app ucr set ... does not trigger it. For appbox, this has been equivalent to univention-app configure, but was always discouraged. Now they actually differ.
Please also add "configure" support in uivention-app dev-regenerate-meta-inf and repo-ng create_appcenter_json.py.
(In reply to Felix Botner from comment #3) > Please also add "configure" support in uivention-app dev-regenerate-meta-inf > and repo-ng create_appcenter_json.py. Done. Live in create_appcenter_json.py and also in the App Provider Portal
OK - appcenter runs configure script OK - yaml fixed the test merge to 4.2 -> Bug #44750
<http://errata.software-univention.de/ucs/4.1/432.html>