* N°7306 - Use iTop configuration settings to run unattended installation (instead of XML file settings)
* 7306 - fix infinite loop with db_tls.ca null
* 7306 - complete fields to use from itop configuration instead of XML setup
* fix using default language from conf
* 6365 - temp work
* 6365 - add option to select modules from installation.xml
* 6365-select modules option in unattended install
* 6365 - pass env to service + debug failed test
* 6365 - debug ci again + separate process annotation
* 6365 - fix test + cleanup
* 6365 - ci using use_installation_xml mode
* 6365 - ci using use_installation_xml mode
* 6365 - pass selected_modules to unattended
* N°6365 - Compute selected modules based on selected extensions coming from XML setup
* switch constr parameters and fix call from unattended cli
* 6365 - use use_installation_xml for unattended install only when no selected modules already provided
* test ci XML setup including selected extensions but no modules
* test ci installing iTop without selected modules/extenesions: guess via installation.xml
* same but without even providing XML setup - comment it in ci_description.ini
* 7306 - cleanup requires
* use infra master
* N°6365 - make current unattended CLI work with any iTop version (CLIPage compatibility)
* N°6365 - log which modules will be installed during setup
* N°6365 - unattended documentation + bash helper
* 6365- fix warning due to copies index access
* 6365 - enhance traces feedback to understant which and how modules are computes
* 6365 - enhance bash CLI + doc
* 6365 - fix require clipage compatibility
* 6365 - add return for better cli ouput
* 6365 - enhance ouput messages
* Document the usage and harmonize argument names (still not perfect)
* 6365 - fix use of new param param-file
* 6365 - fix test + vardump cleanup
* N°6365 - use underscore for unattended install options as advices in the PR
* 6365 -enhance test by using PHP_BINARY
---------
Co-authored-by: Romain Quetiez <romain.quetiez@combodo.com>
The flag consists of the new `data/.compilation-symlinks` file, which is included in the code base (but not available in the Combodo packages).
It will be used and generated if and only if :
* we are on a dev env (`\utils::IsDevelopmentEnvironment`)
* the `symlink` PHP function exists
The flag is generated low level in the compiler (\MFCompiler::DoCompile)
In the setup, if the flag is present and all conditions are met then a new option will be displayed in the "Miscellaneous Parameters" wizard step. When unchecking/checking the flag will be updated accordingly by an ajax query.
All other compiler consumers (Designer / Hub connectors, Core Update, scripts using `RunTimeEnvironment` class) will :
* if they provide a value for the symlink option, it will be used
* otherwise the flag will be used instead, if conditions are met
- The code now uses the standard extension method (using interfaces)
- the metamodel can now filter on iModuleExtension in order to leverage extensions modularity (see MetaModel::EnumPlugins second param)
- during the setup, there is no pawsord policy control
- there is now a default policy
- new (more precie) translation reflecting the default policy
- fix CI?
* remove require() calls (now we have an autoloader \o/)
* change cache policy in utils::GetConfig
* set config in utils class from ApplicationInstaller
* backup : add missing PHPDoc
* backup : use a config object instead of each parameter attribute
* CMDBSource::InitServerAndPort : remove static attribute dependency, change visibility
* setup : generate a config instance to use in backup
* backup : add TLS params if needed to the mysqldump call
SVN:trunk[5375]
