fix(gcp_pubsub): remove conflicting `request_timeout` option

Since the buffer worker schema already contains that configuration,
having it two places can lead to quite confusing behavior.
This commit is contained in:
Thales Macedo Garitezi 2023-03-01 11:49:41 -03:00
parent 167b7a212f
commit 9b087a21f5
3 changed files with 2 additions and 12 deletions

View File

@ -79,15 +79,6 @@ fields(bridge_config) ->
desc => ?DESC("max_retries")
}
)},
{request_timeout,
sc(
emqx_schema:duration_ms(),
#{
required => false,
default => <<"15s">>,
desc => ?DESC("request_timeout")
}
)},
{payload_template,
sc(
binary(),

View File

@ -282,7 +282,6 @@ gcp_pubsub_config(Config) ->
"bridges.gcp_pubsub.~s {\n"
" enable = true\n"
" connect_timeout = 1s\n"
" request_timeout = 1s\n"
" service_account_json = ~s\n"
" payload_template = ~p\n"
" pubsub_topic = ~s\n"

View File

@ -33,7 +33,7 @@
connect_timeout := emqx_schema:duration_ms(),
max_retries := non_neg_integer(),
pubsub_topic := binary(),
request_timeout := emqx_schema:duration_ms(),
resource_opts := #{request_timeout := emqx_schema:duration_ms(), any() => term()},
service_account_json := service_account_json(),
any() => term()
}.
@ -71,7 +71,7 @@ on_start(
payload_template := PayloadTemplate,
pool_size := PoolSize,
pubsub_topic := PubSubTopic,
request_timeout := RequestTimeout
resource_opts := #{request_timeout := RequestTimeout}
} = Config
) ->
?SLOG(info, #{