Duplicate and dependency errors about rabbitmq-cloudwatch-exporter HOT 4 CLOSED

I will fix it asap.

from rabbitmq-cloudwatch-exporter.

Release updated, could you please confirm it works?

from rabbitmq-cloudwatch-exporter.

looks like it does the trick, yep :)

I have a question though : Why do you keep replacing binaries in the 1.0.0 release instead of making new release each time ?

This is problematic as a fixed version in infra as code will result in an error at installation in the future, which is what lead me here in the first place.

I would advise to make a new release each time, like 1.0.1, 1.0.2 or so.

from rabbitmq-cloudwatch-exporter.

These are rare occasions in which we need to update one of the plugin dependency versions due to bugs or vulnerabilities. As the plugin package does not change, its version remains the same. RabbitMQ unfortunately does not provide a robust way to handle plugins packaging. Hence we need to provide all dependencies generated at build time together with the plugin package.

In particular, this was related to issue #34. There might be a second case for issue #33.

A script which downloads all the assets from a release (via for example GH APIs) rather than point to the single ones would most likely mitigate these issues.

from rabbitmq-cloudwatch-exporter.