You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run molecule create, and observe that an error is shown.
$ molecule create
CRITICAL Failed to validate /runner/home/username/myrole/molecule/default/molecule.yml
["{'http_proxy': 'http://127.0.0.1:8080'} is not of type 'array'"]
In molecule 4.0.1, this works as expected. In 4.0.2 this behaviour has broken, and we must change the env keys in our molecule.yml to an array. If this is intentional, it's a breaking change and it should be mentioned it in the release note - hopefully it's just a bug caused by the json schema changes.
The text was updated successfully, but these errors were encountered:
Issue Type
Molecule and Ansible details
Molecule installation method (one of):
Ansible installation method (one of):
Detail any linters or test runners used:
Desired Behavior
Molecule 4.0.2 should work with the same molecule.yml as 4.0.1
Actual Behaviour
To reproduce, generate a standard molecule role as follows:
Modify molecule.yml to add env as follows
Run
molecule create
, and observe that an error is shown.$ molecule create CRITICAL Failed to validate /runner/home/username/myrole/molecule/default/molecule.yml ["{'http_proxy': 'http://127.0.0.1:8080'} is not of type 'array'"]
In molecule 4.0.1, this works as expected. In 4.0.2 this behaviour has broken, and we must change the env keys in our molecule.yml to an array. If this is intentional, it's a breaking change and it should be mentioned it in the release note - hopefully it's just a bug caused by the json schema changes.
The text was updated successfully, but these errors were encountered: