Bug in test function not interpreting test readiness correctly when 0 tasks are enabled (Does not affect production)

[wilkermichael]

Describe the bug

The function used to detect CTS test readiness, currently doesn't work if the enabled tasks in CTS are '0' as expected. This is useful in the case where we don't care about tasks running for a particular test, and just want to test other CTS behavior.

This does not affect anything in production.

Versions

Consul Terraform Sync

consul-terraform-sync v0.6.0

Actual Behavior

If a test starts up CTS with a configuration with all tasks disabled, and the test attempts to stop CTS, the test will fail due to being unable to stop cleanly.

Steps to Reproduce

1. Go to the following test, which doesn't require a task to run:
   

   consul-terraform-sync/e2e/registration_test.go

   Lines 129 to 144 in ba8b4ac

   	func TestE2E_ServiceRegistration_DeregisterWhenStopped(t *testing.T) {
   	setParallelism(t)
   	srv := newTestConsulServer(t)
   	defer srv.Stop()
   	tempDir := fmt.Sprintf("%s%s", tempDirPrefix, "cts_stop_deregister")
   	cleanup := testutils.MakeTempDir(t, tempDir)
   	defer cleanup()
   	id := "cts-01"
   	configPath := filepath.Join(tempDir, configFile)
   	config := baseConfig(tempDir).appendID(id).
   	appendConsulBlock(srv).appendTerraformBlock().
   	appendModuleTask("disabled_task", "mkam/hello/cts",
   	"enabled = true")
   	config.write(t, configPath)

2. Change the last line from "enabled = true" to "enabled = false"
3. This test will fail because CTS was unable to stop cleanly (because CTS was not ready for testing yet)