root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions 6 Packages Projects Releases Wiki Activity
rabbitmq-server/deps/rabbitmq_peer_discovery_common/include/rabbit_peer_discovery.hrl

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

38 lines
1.6 KiB
Erlang
Raw Normal View History

Switch to MPL2
2020-07-14 21:04:17 +08:00
%% This Source Code Form is subject to the terms of the Mozilla Public
%% License, v. 2.0. If a copy of the MPL was not distributed with this
%% file, You can obtain one at https://mozilla.org/MPL/2.0/.
Initial cut at revisited configuration module This module is aware of environment variables, just like in rabbitmq-autocluster, for ease of migration.
2017-04-20 18:44:29 +08:00
%%
(c) year bump: 2022 => 2023
2023-01-02 12:17:36 +08:00
%% Copyright (c) 2020-2023 VMware, Inc. or its affiliates. All rights reserved.
Initial cut at revisited configuration module This module is aware of environment variables, just like in rabbitmq-autocluster, for ease of migration.
2017-04-20 18:44:29 +08:00
%%
rabbitmq_peer_discovery_{common,consul}: Switch to Logger macros ... from `rabbit_log:*` calls. Many rabbitmq_peer_discovery_consul testcases are executed outside of a RabbitMQ server node. When we had Lager `parse_transform` enabled, calls to `rabbit_log` were converted to something which happened to not break when executed outside of RabbitMQ. Now that `rabbit_log` calls are kept (there is no `parse_transform`), the missing dependency to rabbit_common in the common_test node surfaces nad hilights the breakage which has always been there. Calls to `rabbit_log` are now replaced with Logger macros and this works again, even in the context of the common_test node.
2021-03-04 21:22:48 +08:00
-include_lib("rabbit_common/include/logging.hrl").
-define(RMQLOG_DOMAIN_PEER_DIS, ?DEFINE_RMQLOG_DOMAIN(peer_discovery)).
Set connect and request timeouts httpc:request has a default timeout of infinity. This PR ensures that both the connect and request phase uses a timeout Part of rabbitmq/rabbitmq-peer-discovery-aws#25
2019-01-12 04:24:57 +08:00
% rabbitmq/rabbitmq-peer-discovery-aws#25
% Note: this timeout must not be greater than the default
% gen_server:call timeout of 5000ms. This `timeout`,
% when set, is used as the connect and then request timeout
% by `httpc`
-define(DEFAULT_HTTP_TIMEOUT, 2250).
fix types
2023-12-13 06:50:15 +08:00
-type peer_discovery_config_value() :: port()
| atom()
| integer()
| string()
| proplists:proplist()
| map()
| list()
| undefined.
Initial cut at revisited configuration module This module is aware of environment variables, just like in rabbitmq-autocluster, for ease of migration.
2017-04-20 18:44:29 +08:00
-record(peer_discovery_config_entry_meta,
{env_variable :: string(),
default_value :: peer_discovery_config_value(),
type :: atom()}).
Migrate away from http_uri for warning-free OTP 23 compatibility This changes the API of rabbit_peer_discovery_httpc. All callers in RabbitMQ peer discovery plugins were updated accordingly. While at it, fix some issues discovered by Dialyzer. Note: uri_string is only available starting with OTP 21.
2019-12-29 22:04:03 +08:00
-type(peer_discovery_config_entry_meta() :: #peer_discovery_config_entry_meta{
type :: atom(),
env_variable :: string(),
default_value :: peer_discovery_config_value()
}).