Composer install won't finish about ansible-symfony2

[maschmann]

Hi bonswouar,

that's right: Will investigate later tonight. Strangely this did not occur during the sf2 default install (at least according to the last travis test). Maybe a change in the sf2 installation?
check: https://travis-ci.org/servergrove/ansible-symfony2

The parameters are processed when there is no parameters.ini and only a parameters.dist file, but I'm not sure why the interactive shell is popping up at that point.

And: Thanks for reporting 👍

[maschmann]

@bonswouar : I tried it locally with current 2.6 and 2.7 versions of symfony and the paramerters.yml gets created. Do you have any specialities in your deployment?
What environment do you use? sf version?

[bonswouar]

Thank you for your investigation @maschmann !

Actually yes, I have some specialities in my deployment.. I use Incenteev/ParameterHandler to handle multiple parameter files.
Precisely, I've got 3 parameters.yml files with that configuration in composer.json :

        "incenteev-parameters": [{
            "file": "apps/config/common_parameters.yml"
        },
        {
            "file": "apps/app1/config/parameters.yml"
        },
        {
            "file": "apps/app2/config/parameters.yml"
        }]

But it shouldn't change the behaviour of composer handling those .dist files ?!

[maschmann]

@bonswouar that's actually triggered by the composer post-install/upgrade hook:

    "scripts": {
        ...
        "post-install-cmd": [
            "Incenteev\\ParameterHandler\\ScriptHandler::buildParameters",
            ...
        ],
        "post-update-cmd": [
            "Incenteev\\ParameterHandler\\ScriptHandler::buildParameters",
            ...
        ]
    },
    "extra": {
        ...
        "incenteev-parameters": {
            "file": "app/config/parameters.yml"
        },
        ...
    }

But it's only framework-stuff triggered by the install/update.
During further research, I found a mentioning of non-interactive mode for composer here and as params here. I'll integrate into composer calls and test :-)
As far as I know, the interactive mode shouldn't be triggered if env > dev. Which env are you deploying?

// Edit

Try configuring the composer command like this:
symfony2_project_composer_opts: '--no-dev --optimize-autoloader --prefer-dist --no-interaction'