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: Hide Other Warehouses and Stages when Filtering by Warehouse #2526

Open
2 of 3 tasks
BenjaminNeale-Heritage opened this issue Sep 13, 2024 · 1 comment
Open
2 of 3 tasks

Comments

@BenjaminNeale-Heritage
Copy link

Checklist

  • I've searched the issue queue to verify this is not a duplicate feature request.
  • I've pasted the output of kargo version, if applicable.
  • I've pasted logs, if applicable.

Proposed Feature

It is possible to filter by warehouse in the Kargo UI (refer image below). However, this only seems to filter the freight timeline. It does not seem to filter the DAG pipeline which continues to display stages that are not connected to the warehouse.
image

Motivation

This would help when a project has multiple warehouses.

Suggested Implementation

Hide warehouses and stages in the DAG that are not connected to the warehouse filter being used.

Example

The DAG showing all warehouses.
kargo-filter-all-warehouses

The DAG filtered by the "auth" service (which is configured for all stages).
kargo-filter-auth-warehouse

The DAG filtered by the "config" service (which is only configured for the 'labdev' stage).
kargo-filter-config-warehouse

Version

I'm running Kargo v0.8.7. I looked through the open tickets and the tickets completed for Kargo v0.9.0 and couldn't see this so I hope it isn't a duplicate.

@BenjaminNeale-Heritage BenjaminNeale-Heritage changed the title Hide Other Warehouses and Stages when Filtering by Warehouse Feature Request: Hide Other Warehouses and Stages when Filtering by Warehouse Sep 13, 2024
@krancour
Copy link
Member

I understand the request, and without dismissing it outright, I have mixed feelings here.

On the one hand, if I had multiple DAGs in one Project that didn't really intersect/overlap at all, I think that this proposed feature would feel very useful to me. i.e. Imagine microservice A and B in the same Project, and they both have their own distinct Warehouses and Stages and are "parallel" to one another and related to one another only from a management perspective -- logically part of the same Project, with the same set of users responsible for them. Selecting the Warehouse for microservice A, thereby hiding the warehouse for B and all the Stages connected to it feels like it would help me to focus on microservice A.

On the other hand, when the situation is more like the one presented in the screenshots, I feel as if a relatively important piece of the overall picture is missing. In some way it feels "hazardous" to me to lose sight of the fact that the loaddev Stage, for instance, consumes Freight from multiple Warehouses. It's a rather important detail.

I would be very interested to hear @jessesuen's perspective on what he feels the right behavior may be here.

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

No branches or pull requests

2 participants