again, it's been debated that we shouldn't be allowed to completely drop
apis.
in regards to deprecation, how do you make this deprecation known? also,
this goes beyond the client. if we deprecated in the client we should
really have the endpoint deprecated in API as well.
On 05/11/2015
i'm sort of torn on this item. there's a general feeling that regarding
api, nothing should be dropped so i'm hesitant to actually deprecate it.
i think changing the data also is very dangerous when it comes to
compatibility (even though keeping it increases inconsistency).
maybe the better
I don't think we need two APIs to act duplicated functionalities, the
"sample-list -m" command actually invoke API "GET
/V2/meters/", it is more like a meter related API, not
sample. I personally prefer to mark the "sample-list -m" command
deprecated and dropped in future cycle. is this
Hi,Here is an open bug : https://bugs.launchpad.net/ceilometer/+bug/1497073Is it a bug or not?For the command "ceilometer sample-list --meter cpu", it calls "/v2/meter" API and return the OldSample objectswhich return body is different from "ceilometer sample-list --query 'meter=cpu'".To fix this
