enable tenants selector

[dmitryk-dk]

Enable the tenants selector into the datasource settings.

If the backend doesn't support the endpoint the previous inputs will be used

Related issue: #475

[Loori-R]

Do I understand correctly that the user can select ProjectID and AccountID independently from each other?
Shouldn’t they be selected as a pair (i.e., only valid ProjectID:AccountID combinations)?

[dmitryk-dk]

Do I understand correctly that the user can select ProjectID and AccountID independently from each other? Shouldn’t they be selected as a pair (i.e., only valid ProjectID:AccountID combinations)?

yep. But if we have

{[accountid:5, projectid:1], [accountid: 5, projectid:2], [accountid: 5, projectid:3]}

which to choose (first)?
If yes i will update the logic

[Loori-R]

I think the simplest approach is to have a single selector with values in the AccountID:ProjectID format (same as in vmui and the format returned by VictoriaMetrics). This way the user always selects a valid pair.

An alternative would be to keep two fields and filter ProjectID options based on the selected AccountID, but this seems less convenient - the user would first have to change the AccountID in order to access a different ProjectID.

[dmitryk-dk]

I think the simplest approach is to have a single selector with values in the AccountID:ProjectID format (same as in vmui and the format returned by VictoriaMetrics). This way the user always selects a valid pair.

An alternative would be to keep two fields and filter ProjectID options based on the selected AccountID, but this seems less convenient - the user would first have to change the AccountID in order to access a different ProjectID.

Oki doki, will update to one selector :)

[Loori-R]

LGTM!

[arturminchukov]

LGTM!