wp-now: ifAlreadyInstalled does not work

[timofey-drozhzhin]

ifAlreadyInstalled option previously introduced in WordPress/wordpress-playground#1244 does not seem to work.

Steps to reproduce

Create blueprint.json with the following:

{
  "$schema": "https://playground.wordpress.net/blueprint-schema.json",
  "steps": [
    {
      "step": "installPlugin",
      "pluginZipFile": {
        "resource": "wordpress.org/plugins",
        "path": "block-enhancements"
      },
      "ifAlreadyInstalled": "skip"
    }
  ]
}

and run wp-now start --blueprint=blueprint.json

Resulting error:

[adamziel]

@timofey-drozhzhin That's a wp-now issue so I'll move it to the playground-tools repo. Here's a Blueprint builder example where that attribute works. wp-now is a separate app and not a part of Playground core. I think updating the packages and releasing a new version would solve the problem here, I'm just not sure if it's a simple version bump or if there were any breaking Playground changes to accommodate.

Also, the Blueprint you've shared needs a minor adjustment: path should be slug.

[ryandejaegher]

@timofey-drozhzhin happy to hear I'm not the only one that ran into this issue.

@adamziel What is the distinction/separation between wp-now and WP Playground? I know wp-now is the npm/cli tool but I'm confused about why the updates don't happen in parallel.

I ran into issues in the earlier days of wp-now where the documentation on WP Playground talked about being able to run blueprint.json files but it took a bit for wp-now to catch up.