Add possibility to switch between Composer 1 and Composer 2

[norgeindian]

Magento 2.4.1 supports only Composer1 whereas Magento 2.4.2 supports Composer 2 as well.
So it would be great if this could be a setting to switch between the versions

[Den4ik]

@norgeindian composer1 and compose2 alredy preinstalled.
You may use it by composer or composer2 commands

[norgeindian]

@Den4ik , just tried it. Does not work in the warden shell.
Even in the current develop branch, composer2 is not found.
And nevertheless it would be great, if only one of both would be installed, so that I don't have to think about which one to use in a specific project

[Den4ik]

@norgeindian Looks like you have older pulled docker images. Please, try to pull latest
Just checked with latest image
docker run --rm -it wardenenv/php-fpm:7.2 bash

Command to help update all pulled images:
docker images | grep -v REPOSITORY | awk '{image=$1":"$2; print image}' | xargs -L1 docker pull

[norgeindian]

@Den4ik , thanks a lot for the hint. You are right, now it works.
Anyway, @davidalger , what do you think about adding a general env setting here, so that the composer version for each environment is fixed?
Maybe that could be done in images/php-fpm/Dockerfile?

[davidalger]

@norgeindian @Den4ik This is a wonderful idea. Added support for this to the image entrypoint. See #300 for details on it. Next steps is to update all usages of php-fpm based images in docker-composer config to pass the value through, should be relatively simple to do.

I grok the awk/xargs usage above to pull all the images. :) Pro-tip: If you only want to pull latest images used by a given environment: warden env pull will do the trick, then the usual warden env up to recreate containers with the new images.

[davidalger]

COMPOSER_VERSION=2 in the .env file will now cause 'composer' in the container to be v2 instead of v1. The default remains v1 due to v2's newness and to ensure compatibility. It may be changed to default v2 at some point in the future once folks have had more time to update and use it.

[Brengineer]

I'm not sure if something is hard-coded here, but when I have COMPOSER_VERSION=2.1 (as required by Magento 2.4.4) in my .env file, the version is still 1.x in the Warden shell. However, if I revert to exactly COMPOSER_VERSION=2 in the .env file, then the version is 2.x in the Warden shell (after running $ warden env up of course).

[alinalexandru]

That variable just swich composer version from 1.x to 2.x There is no functionality to specify the composer version exactly (like 2.1,2.2, etc)

…

On Fri, Aug 12, 2022, 06:16 Brendan Tull ***@***.***> wrote: I'm not sure if something is hard-coded here, but when I have COMPOSER_VERSION=2.1 (as required by Magento 2.4.4) in my .env file, the version is still 1.x in the Warden shell. However, if I revert to exactly COMPOSER_VERSION=2 in the .env file, then the version is 2.x in the Warden shell (after running $ warden env up of course). — Reply to this email directly, view it on GitHub <#296 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAVO7EVWP53UABJZMXPNOYTVYW6X5ANCNFSM4XPGXMJA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[sohelrana09]

How to make a specific composer version @alinalexandru? Did you manage @Brengineer?

[alinalexandru]

You can not run a specific version. You can specify to use composer 1.x or 2.x by setting in .env the variable COMPOSER_VERSION

If you set COMPOSER_VERSION=2, the composer version will be 2.2.5, at this moment.
If you set COMPOSER_VERSION=1, the composer version will be 1.10.23, at this moment.

If you need a specific version, there are 2 options:

• create your one image, and use them
• install required composer version after each warden env up.

[sohelrana09]

Thanks @alinalexandru. Our case composer version is 2.3 when we checkout master branch which cause the installation problem for M2.4.4. Not sure which warden version we use for composer 2.2.x.

[alexandrosk]

Is there a way to specify 2.2.10 when using COMPOSER_VERSION=2 instead of 2.3 ?

[navarr]

Is there a way to specify 2.2.10 when using COMPOSER_VERSION=2 instead of 2.3 ?

You can specify 2.2 to get the latest 2.2.x