Now that we have cloud image metadata for Canonistack, the hard coded
image id and instance type used for live tests are no longer required.
Another change is that the live tests now create a test "container"
in which to upload the fake tools to the public bucket. This allows
any specified public bucket to be used to read the image metadata files
but does not risk any legitimate tools in that public bucket being
deleted.
The clean up for the live tests only removes the fake tools from the
test "container" and leaves the other public bucket files untouched.
*** Submitted:
Remove hard coded Canonistack image id
Now that we have cloud image metadata for Canonistack, the hard coded
image id and instance type used for live tests are no longer required.
Another change is that the live tests now create a test "container"
in which to upload the fake tools to the public bucket. This allows
any specified public bucket to be used to read the image metadata files
but does not risk any legitimate tools in that public bucket being
deleted.
The clean up for the live tests only removes the fake tools from the
test "container" and leaves the other public bucket files untouched.
R=dimitern, jameinel, fwereade /codereview. appspot. com/8812053
CC=
https:/
https:/ /codereview. appspot. com/8812053/