Fixed an issue where attacks were incorrectly labeled
when Gremlin fails to notify
during teardown of the network impact.
Fixed a class of issues where Gremlin would not retry requests that failed with transient network errors. This sometimes lead to failing container attacks that should otherwise succeed.
For users running Gremlin in the Docker container runtime, rollbacks against container targets no longer require provisioning a second container instance, which results in faster rollbacks.
Gremlin provides more context to errors stemming from failed http requests to
For users running Gremlin on AWS, more error information is printed to the log file when AWS metadata cannot be retrieved.