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
We don't want to include the header in the GitHub releases, as we will
end up with two headers with the same value. Considering that we are
thinking of fully automating patch releases, this change helps with that
too. Small steps.
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Mentioning the release-notes change is important, as we want to change
the way contributors (including us) make changes. Release notes should
be part of the change, and the reasoning behind it is in the 3.9.2
release notes.
Removing any mention of the Grafana dashboard as it is not something
that end-users will see. We didn't mention it in the 3.9.1 release
notes, and we are even thinking of removing all Grafana dashboards from
rabbitmq_prometheus. This explains why:
https://github.com/rabbitmq/release-engineering/issues/11#issuecomment-887627938
cc @michaelklishin
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Keeping them in this repo might encourage more people to update
them as changes are merged, and simplify release automation a bit.
So let's try it. Per suggestion from @gerhard.
Iliia Khaprov
Michael Klishin
Gerhard Lazu
Michael Klishin