Skip to content
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

Feature request: list all ressources #160

Open
sdouche opened this issue Nov 4, 2017 · 5 comments
Open

Feature request: list all ressources #160

sdouche opened this issue Nov 4, 2017 · 5 comments
Labels

Comments

@sdouche
Copy link

sdouche commented Nov 4, 2017

Hi,
It's always unpleasant to search your resources in your regions. It would be cool to have an awless ls all option list all resources created.

Regards.

@simcap
Copy link
Contributor

simcap commented Nov 5, 2017

This is a great idea indeed and it is on our roadmap since the AWS meetup in Berlin! So yes we will support multi region listing as it is definitely a needed feature that actually other CLI do not support.

Right now, we are in the process of finishing a major (re)design that improve the availability of our AWS modelling and that will allow great features to come. That is why the 0.1.6 is not out yet.

Anyway, back to our multi region support. Obviously, when doing a multi-region listing command, we will not be able to ask every AWS region because: too many, a bit silly, throttling issues, too many resource at once in RAM.

So in my opinion when doing a multi-region query we will rather focus on a subset of the regions. There are multiple ways of getting this subset before fetching and they could be:

  • dynamically with a csv region flag (not great but should be available)
  • configured by the user in advance in awless and obviously updatable.
  • look at what regions have been sync so far locally (in ~/.awless/aws/rdf/...) if no configuration
  • ... or other ideas.

Any ideas to make this a great feature are welcome in this issue.

@simcap
Copy link
Contributor

simcap commented Nov 5, 2017

Also we need to distinguish between: listing all instances in multi-region; listing all resources in multi-region; listing all resources in 1 region. Those are not the same features.

Right now I am understanding that we talk about the natural extension awless list instances --multi-regions ....

(Note that in the meantime: to see all the resources in a region you can do awless show us-west-2 for instance; to see all resources in your synced regions there is an hidden command awless web where you can browse resources ...)

@sdouche
Copy link
Author

sdouche commented Nov 5, 2017

Hi @simcap
I was not very clear in my proposal: the goal is to list all resources from one region. It's ok to me write the command for each region. The implementation would be something like this:

for each kind of resources
    result = get resources
    if result not null
        display

Very simple implementation but extremely useful (I think).

@fxaguessy
Copy link
Contributor

Hello @sdouche, thanks for the suggestion.

The difficulty for listing all types of resources in one command is the choice of the columns to display (as entities with different types have different properties). It would be strange to display several tables one after the other with different number of columns and columns names.
One possible solution for that has been experimented in the (hidden) command awless list infra (or access/storage/...). But as the result of this command was not totally satisfying (too verbose ?) and we did not have a clear use case for it, we did not make it public, nor create a list all command.

What is your use case ? Do you have a better idea to display the results of such a command ?

@improved-broccoli
Copy link

improved-broccoli commented Dec 21, 2017

Only common columns could be showed (ARN, resource type, creation date, ...).
Imagine I want to find out which resources are not managed through CloudFormation in a specific region, I could list all stack resources arn then diff it with the list of all resources arn in the region.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants