As mentioned in https://github.com/18F/domain-scan/issues/138, sslyze is stalling out for unknown reasons. This is the main reason the scans have stalled for the last month on Pulse. Since we're not even using sslyze for actual Pulse stuff, but instead capture it during the scan for other off-band purposes, I'm yanking it from the Pulse pipeline at least temporarily.
As mentioned in https://github.com/18F/domain-scan/issues/138, sslyze is stalling out for unknown reasons. This is the main reason the scans have stalled for the last month on Pulse. Since we're not even using sslyze for actual Pulse stuff, but instead capture it during the scan for other off-band purposes, I'm yanking it from the Pulse pipeline at least temporarily.
We can do these scans from a separate DotGov server if need be for the near future, while https://github.com/18F/domain-scan/issues/138 is resolved.