Support definition import from a remote location over HTTPS #3249
Comments
This was referenced Jul 29, 2021
michaelklishin
changed the title
|
Apparently I haven't finished writing the description when I first filed this. Hope this makes more sense now :) |
michaelklishin
added a commit
that referenced
this issue
Aug 14, 2021
The classic local filesystem source is still supported using the same traditional configuration key, load_definitions. Configuration schema follows peer discovery in spirit: * definitions.import_backend configures the mechanism to use, which can be a module provided by a plugin * definitions.* keys can be defined by plugins and contain any keys a specific mechanism needs For example, the classic local filesystem source can now be configured like this: ``` ini definitions.import_backend = local_filesystem definitions.local.path = /path/to/definitions.d/definition.json ``` ``` ini definitions.import_backend = https definitions.https.url = https://hostname/path/to/definitions.json ``` HTTPS may require additional configuration keys related to TLS/x.509 peer verification. Such extra keys will be added as the need for them becomes evident. References #3249
11 tasks
mergify bot
pushed a commit
that referenced
this issue
Aug 17, 2021
The classic local filesystem source is still supported using the same traditional configuration key, load_definitions. Configuration schema follows peer discovery in spirit: * definitions.import_backend configures the mechanism to use, which can be a module provided by a plugin * definitions.* keys can be defined by plugins and contain any keys a specific mechanism needs For example, the classic local filesystem source can now be configured like this: ``` ini definitions.import_backend = local_filesystem definitions.local.path = /path/to/definitions.d/definition.json ``` ``` ini definitions.import_backend = https definitions.https.url = https://hostname/path/to/definitions.json ``` HTTPS may require additional configuration keys related to TLS/x.509 peer verification. Such extra keys will be added as the need for them becomes evident. References #3249 (cherry picked from commit f3a5235)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This was discussed before docker-library/rabbitmq#508 but can be particularly useful with
such "service containers" where mounting of a local configuration file may or may not be possible.
More importantly, the goal in those environmentswas not necessarily to override anything in
rabbitmq.confbut to set upand thus allow for remote connections since default user can only connect from localhost by default.
If the definition import mechanism could be extended to consume definition files from remote HTTPS endpoints and not just a local file,
this would be a decent alternative.
The text was updated successfully, but these errors were encountered: