Open tbauriedel opened 5 months ago
Did you try to set the environment variables locally?
export MYENVIRONMENTVARIABLE=myvalue
I guess, we could set some automatically, but I think it helps to have some control about some parts of the checks.
If that fixes your problem, we need to put it into the documentation. It shouldn't be misleading.
I know. But I expected all molecule tests should work out of the box.
As far as I know, elasticsearch 7 will rotate out of the collection soon. After that, we could adjust the variables in the scenarios to work with 8.
Please try to fill out as much of the information below as you can. Thank you!
Which version contains the bug?
No response
Describe the bug
Molecule tests have a reference to environment variables. Example
However, the environments are only defined within the GitHub workflow. If you try to run local molecule tests (
molecule test -s <scenario>
), they fail due to the missing environments. So you will always have to run the whole pipeline local.How to recreate the bug?
No response