We should add an unless check for Puppet so that if composer.lock exists then we don't want to run the composer install command.

Apologies for not having the relevant details for below
I'll endeavor to get this information tomorrow and update here

1. What operating system do you use?

??? (Possibly Windows, maybe Mac)

2. What version of Vagrant are you running?

??? (I believe the latest, a fresh install)

3. Are you using VirtualBox or VMWare and which version are you using?

??? (I'm guessing Virtual Box)

4. Do you have a custom YAML file? If so, what does it contain?
   (Please paste in your chassis.local.yaml file)

A HM Project I work on

5. Do you have any Chassis other extensions installed? If so, what are they?

The issue appears to be isolated to the Composer Chassis extension

Error: [vagrant] default: Error: Evaluation Error: Error while evaluating a Resource Statement, Unknown resource type: 'install' (file: /vagrant/extensions/composer/modules/composer/manifests/init.pp, line: 63, column: 4) on node lol.local

This was introduced in the 88c47f7 commit

[vagrant]     default: Get:45 http://archive.ubuntu.com/ubuntu bionic-backports/main i386 Packages [2,516 B]
[vagrant]     default: Get:46 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages [2,512 B]
[vagrant]     default: Get:47 http://archive.ubuntu.com/ubuntu bionic-backports/main Translation-en [1,644 B]
[vagrant]     default: Get:48 http://archive.ubuntu.com/ubuntu bionic-backports/universe i386 Packages [4,024 B]
[vagrant]     default: Get:49 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [4,028 B]
[vagrant]     default: Get:50 http://archive.ubuntu.com/ubuntu bionic-backports/universe Translation-en [1,856 B]
[vagrant]     default: Fetched 32.5 MB in 16s (2,030 kB/s)
[vagrant]     default: Reading package lists...
[vagrant]     default: Reading package lists...
[vagrant]     default: Building dependency tree...
[vagrant]     default: Reading state information...
[vagrant]     default: puppet is already the newest version (5.4.0-2ubuntu3).
[vagrant]     default: 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
[vagrant] ==> default: Running provisioner: shell...
[vagrant]     default: Running: inline script
[vagrant]     default: Error: Evaluation Error: Error while evaluating a Resource Statement, Unknown resource type: 'install' (file: /vagrant/extensions/composer/modules/composer/manifests/init.pp, line: 63, column: 4) on node lol.local
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Open http://lol.local/wp-admin/ in your browser? [y/N]

I just noticed this while working on: Chassis/phpMyAdmin#8

Without this requirement a fresh provision will throw an error:

==> default: Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install php5.6-dev' returned 100: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: E: Unable to locate package php5.6-dev
==> default: E: Couldn't find any package by regex 'php5.6-dev'
==> default: Error: /Stage[main]/Composer/Package[php5.6-dev]/ensure: change from purged to latest failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install php5.6-dev' returned 100: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: E: Unable to locate package php5.6-dev
==> default: E: Couldn't find any package by regex 'php5.6-dev'
==> default: Notice: /Package[php-pear]: Dependency Package[php5.6-dev] has failures: true

I've seen some issues with extensions requiring composer failing to install because they require Composer 1.x. We should add the ability to specify major versions.

Currently we have /vagrant/$name we should alter this to $name and change the docs to include paths for /vagrant/... for default installs and /chassis/... for subdirectory installations.

We should add the ability to add options in a .yaml file to composer install

As a developer, I should be able to specify one or more folder paths where I'd like to run composer install.

For a clients project we are having an issue with phpunit being lncluded in one of their composer dependencies and this is some of our code to fail.

For a quick fix we need to add in --no-dev to this extension for now and after that I will open a ticket to correctly implement --no-dev and also address --ignore-platform-reqs feedback #22 (comment) as well and I'll address this on Friday.

Without this users can end up with messages such as: - doctrine/annotations v1.6.0 requires php ^7.1 -> your PHP version (7.0.31) does not satisfy that requirement.

I added a check for composer.lock in #30 but upon reflection I think it would be better to check if the vendor folder instead.

It would be handy to add a check to see if there are updates to composer and run composer update on provisioning.

Getting the following error on provision:

==> default: Error: Duplicate declaration: Package[php7.0-dev] is already declared in file /vagrant/extensions/phpcs/modules/phpcs/manifests/init.pp:24; cannot redeclare at /vagrant/extensions/composer/modules/composer/manifests/init.pp:13 on node eh.local
==> default: Error: Duplicate declaration: Package[php7.0-dev] is already declared in file /vagrant/extensions/phpcs/modules/phpcs/manifests/init.pp:24; cannot redeclare at /vagrant/extensions/composer/modules/composer/manifests/init.pp:13 on node eh.local

We're specifying the following extensions:

- chassis/xdebug
- chassis/sequelpro
- chassis/cavalcade
- chassis/mailhog
- chassis/memcache
- chassis/composer
- chassis/phpcs

We need to refactor this so the error doesn't occur!

As a developer, sometimes I will want to use Composer to install packages before anything else is installed.

Paul Gibbs has done this is in his fork of the extension so we can take inspiration from there.

As a developer I would like to use the latest version of Chassis extensions.

Due to #25 and #22 (comment) I need to improve this extension.

I've seen this happen on a couple of peoples Chassis boxes but I've been unable to replicate it locally to apply a fix.

The manual solution is to run vagrant ssh then sudo apt-get update then exit out of the box and run vagrant provision

I believe we need to make sure apt is updated before we run: https://github.com/Chassis/Composer/blob/master/modules/composer/manifests/init.pp#L10