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
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
On scaleway's console you see your resources per project.
It could help to be able to have the same behavior with the CLI.
Currently, having a default_project_id will not be effective in filters.
How I imagine scw could expose this functionality
The CLI config in ~/.config/scw/cli.yaml could have an option list_per_project.
References
The text was updated successfully, but these errors were encountered:
Codelax
changed the title
config option to filter list with project filter per default
config option to list with project filter per default
Dec 14, 2023
Community Note
Description
On scaleway's console you see your resources per project.
It could help to be able to have the same behavior with the CLI.
Currently, having a default_project_id will not be effective in filters.
How I imagine scw could expose this functionality
The CLI config in ~/.config/scw/cli.yaml could have an option
list_per_project
.References
The text was updated successfully, but these errors were encountered: