tom wanted configuration dependent key delete at end of release tests. do it with cloud build state: delete_keys_at_teardown, which is passed thru the json like any othe python node state, to the test with the cloned cloud.
then that's used in h2o_common.py to decide what to do in tearDownClass. assumes you're using h2o_common.py like in test_release_basic.py (although you could just copy/paste and use without the common)