Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
replace smoke test config files with env #50
Conversation
petevg
commented
Oct 6, 2016
|
LGTM/+1 |
|
So, the downside of this over having a layer option which points to file(s) is that it means we have to copypasta the whole from charms.layer.apache_bigtop_base import Bigtop
Bigtop().run_smoke_tests()Alternatively, could we make the layer option be an entry-point style reference to a callback that generates and returns the config? |
|
Opened #51 to address my comment above at a future date. +1 for merging this now. |
kwmonroe commentedOct 5, 2016
We currently allow charms to specify a smoke_test_configs layer opt,
which is supposed to be files that we source prior to running the
smoke test. This is hard to handle because we don't know if that
file will be an ini, a dotfile, or some other thing that we have to
grok and source.
Seems smarter for the smoke test itself to construct a dict of all
the environment stuff it needs and pass that into the smoke test
runner.
This does that. I do not believe anyone is using the config file
madness, and it certainly didn't do anything in the smoke test
runner function, so I feel like now's the time to get on the right
path.