You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked to make sure that this issue has not already been filed
I am reporting the issue to the correct repository (for multi-repository projects)
Expected Behavior
ecl --config foundit deployment list --region azure-japaneast should return deployments from azure-japaneast region only.
Current Behavior
The aforementioned command returns deployments not only from azure-japaneast. This can be reproed with any region name in the filter as long as the region exists. If you use a non-existent region name the output is as expected:
▶ ecl --config foundit deployment list --region panete
panete is not a valid region in this environment
Possible Solution
Steps to Reproduce
ecl --config foundit deployment list --region azure-japaneast
the deployments API is a global API rather than a region scoped API, the current behaviour is expected and the --region flag won't limit the results per region, we could add a --region-filter flag which would act like this.
Fair enough. A new flag could indeed be useful, however maybe it makes sense to emulate the same filtering we have in the UI? so you could for example pass a filter expression with --filter
e.g. ecl --config foundit deployment list --filter 'region:(azure-japaneast) logging'
We could add --filter which calls the /search endpoint instead of just using a GET, which is what the UI does.
For planning and know how many people would love to see this, I'd appreciate some 👍 on the issue description. I can also change the name of this issue to better reflect what's asked here :)
@PedroPerezElastic commented on Thu Apr 09 2020
Readiness Checklist
Expected Behavior
ecl --config foundit deployment list --region azure-japaneast
should return deployments fromazure-japaneast
region only.Current Behavior
The aforementioned command returns deployments not only from
azure-japaneast
. This can be reproed with any region name in the filter as long as the region exists. If you use a non-existent region name the output is as expected:▶ ecl --config foundit deployment list --region panete panete is not a valid region in this environment
Possible Solution
Steps to Reproduce
ecl --config foundit deployment list --region azure-japaneast
Contents of my
foundit.yaml
:Context
I just wanted to get a list of deployments in a specific region. This is not a blocker to my work.
Your Environment
MacOS Mojave 10.14.6
@marclop commented on Tue Apr 14 2020
This affects SaaS only.
@marclop commented on Thu Jul 09 2020
the deployments API is a global API rather than a region scoped API, the current behaviour is expected and the
--region
flag won't limit the results per region, we could add a--region-filter
flag which would act like this.@PedroPerezElastic commented on Thu Jul 09 2020
Fair enough. A new flag could indeed be useful, however maybe it makes sense to emulate the same filtering we have in the UI? so you could for example pass a filter expression with
--filter
e.g.
ecl --config foundit deployment list --filter 'region:(azure-japaneast) logging'
Thoughts?
@victorgs commented on Thu Sep 17 2020
i found this issue today. just fyi
@marclop commented on Mon Sep 21 2020
We could add
--filter
which calls the/search
endpoint instead of just using a GET, which is what the UI does.For planning and know how many people would love to see this, I'd appreciate some 👍 on the issue description. I can also change the name of this issue to better reflect what's asked here :)
@ppapapetrou76 commented on Fri Apr 09 2021
@marclop this is on the
ecctl
side right?@marclop commented on Wed Apr 14 2021
yeah
The text was updated successfully, but these errors were encountered: