I've noticed an issue in BLT 12 with the new plugin. In 11 and below, my example.local.yml file has config values in it for certain key values. This allows me to run behat locally and in the CI environment because my behat config gets regenerated on the fly.
Specifically, i see this:
features: ${repo.root}
base_url: ${project.local.uri}
drupal_root: ${docroot}
however, in BLT 12 with this new plugin, all of these config values are replaced in my example.local.yml file with their "local" values and getting committed. this means that when I get into a CI environment and my "local" file gets regenerated, the CI environment is getting my "local" environment and not my "CI" environment (which is a problem).
Steps to Reproduce
Create a new project (using drupal-recommended-project)
Composer install
Composer require this blt-behat project
run the behat command
review the example.local.yml file in the tests directory and observe that the config tokens have already been replaced in the example file. the config tokens should persist in the example file and only be replaced in the actual local.yml file.
I've noticed an issue in BLT 12 with the new plugin. In 11 and below, my example.local.yml file has config values in it for certain key values. This allows me to run behat locally and in the CI environment because my behat config gets regenerated on the fly.
Specifically, i see this:
however, in BLT 12 with this new plugin, all of these config values are replaced in my example.local.yml file with their "local" values and getting committed. this means that when I get into a CI environment and my "local" file gets regenerated, the CI environment is getting my "local" environment and not my "CI" environment (which is a problem).
Steps to Reproduce