In delivery_test_kitchen.rb we clearly expect @environment to be passed in, otherwise, why would we parameters[:environment] || {} and not just set it to {} out of the gate?
However, it does not appear that we can actually pass in environment attributes as setting something like:
delivery_test_kitchen 'unit_create' do
driver 'ec2'
suite 'default'
environment('TK_EC2_REGION' => 'us-west-2', 'TK_MACHINE_SIZE' => 't2.micro')
action :test
end
Results in an error "no function environment" or so...
Basically we're making heavy use of environment variables as Team A might not have access to the same EC2 VPCs as Team B. But save pointing to a different region, ami, etc. it's the same process. so we have a .kitchen.yml:
Hello,
In delivery_test_kitchen.rb we clearly expect
@environment
to be passed in, otherwise, why would weparameters[:environment] || {}
and not just set it to{}
out of the gate?However, it does not appear that we can actually pass in environment attributes as setting something like:
Results in an error "no function
environment
" or so...Basically we're making heavy use of environment variables as Team A might not have access to the same EC2 VPCs as Team B. But save pointing to a different region, ami, etc. it's the same process. so we have a .kitchen.yml:
Team A might have a shell script
and Team B gets
What we'd like to see is the ability to pass "arbitrary" environment variables to our Test Kitchen run.
Thanks!