-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export user tags as a list #2667
Comments
This change would make definitions exported on a newer version fail to import on the older releases. The opposite is not true, older definitions will be imported just fine with a trivial amount of effort. Perhaps this should go into |
michaelklishin
added a commit
that referenced
this issue
Dec 9, 2020
as opposed to a comma-separated binary. Part of #2667.
michaelklishin
added a commit
that referenced
this issue
Dec 9, 2020
instead of a comma-separated list in a string. When importing, both formats are now supported (as of the previous commit). Closes #2667.
11 tasks
michaelklishin
added a commit
to rabbitmq/hop
that referenced
this issue
Dec 9, 2020
As of rabbitmq/rabbitmq-server#2667, the format changes from a comma-separated list in a string to a JSON array. Pair: @acogoluegnes.
This was referenced Dec 9, 2020
acogoluegnes
added a commit
that referenced
this issue
Dec 11, 2020
As they are no longer a comma-separated list in a string. References #2667
acogoluegnes
added a commit
to rabbitmq/hop
that referenced
this issue
Dec 15, 2020
Sets also the JSON utilities in a class in the com.rabbitmq.http.client package. This allows to make all those classes package protected and private and usable only from the main Hop package. References rabbitmq/rabbitmq-server#2667 Fixes #235
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is currently exported as a comma-separated list. It would be significantly more convenient to export it as a JSON array. We already do this for virtual host tags, for example.
In order to make this reasonably backwards-compatible we could introduce a new field and/or support both kinds of values for import.
The text was updated successfully, but these errors were encountered: