consul: remove separate API service definition

Used to be necessary for `chat2bridge` which is gone now.

Signed-off-by: Jakub Sokołowski <jakub@status.im>

defaults/main.yml

@@ -16,7 +16,7 @@ matterbridge_nick: bridge
 matterbridge_ens_name: bridge.stateofus.eth
 
 # configuration for API
-matterbridge_api_enabled: false
+matterbridge_api_enabled: true
 matterbridge_api_port: 4242
 
 # configuration for gateways

tasks/consul.yml

@@ -4,24 +4,11 @@
   vars:
     consul_config_name: '{{ matterbridge_service_name }}'
     consul_services:
-      - name: '{{ matterbridge_service_name }}'
+      - id:   '{{ matterbridge_service_name }}'
+        name: '{{ matterbridge_service_name }}'
         tags: ['matterbridge', 'bridge']
         checks:
-          - id: '{{ matterbridge_service_name }}-health'
+          - id:   '{{ matterbridge_service_name }}-health'
-            name: 'MatterBridge health'
-            type: 'script'
-            script: '/usr/bin/pgrep -xl matterbridge'
-
-- name: Create Consul service definition for API
-  include_role: name=infra-role-consul-service
-  when: '{{ matterbridge_api_enabled }}'
-  vars:
-    consul_config_name: '{{ matterbridge_service_name }}-api'
-    consul_services:
-      - name: '{{ matterbridge_service_name }}-api'
-        tags: ['matterbridge', 'bridge']
-        checks:
-          - id: '{{ matterbridge_service_name }}-api-health'
             name: 'MatterBridge API health'
-            type: 'http'
+            type: 'tcp'
-            http: 'http://localhost:{{ matterbridge_api_port }}/api/health'
+            tcp:  '0.0.0.0:{{ matterbridge_api_port }}'